Copy a SQL Server Table using VBA

How do I copy a SQL Server Table using VBA?

Below is the code that I used when the table was in an Access back-end
Public Sub CheckCopyTable()
  On Error Resume Next
  Dim acc As Access.Application
  Dim tbl As DAO.TableDef
  Dim strBackend_Path As String
  Dim db As Database
  Dim tdf As TableDef
  
  strBackend_Path = DB_Param("DB_ServerPath") & DB_Param("DB_BackendName")
  Set acc = New Access.Application
  acc.OpenCurrentDatabase (strBackend_Path)
  Set tbl = acc.CurrentDb.TableDefs("Commitment_Outlook_bak")
  If Err.Number <> 0 Then
    If Err.Number = 3265 Then
      Set db = OpenDatabase(strBackend_Path)
      db.TableDefs("Commitment_Outlook_new").Name = "Commitment_Outlook_bak"  'new to bak
    Else
      LogEvt "Error Number " & Err.Number & vbNewLine & Err.Description, vbExclamation, "CheckCopyTable Error (SB-123)", NOMSG
    End If
  End If
  acc.CloseCurrentDatabase
  Set acc = Nothing
End Sub

Open in new window

schmir1Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

schmir1Author Commented:
Anyone have an idea on how to copy tables on a SQL Server?
0
Jim P.Commented:
You would have to do it via the ADO objects.

It would something on the order of a "SELECT * INTO MyNewTable FROM MyOldTable". Or you would have to do it as a

CREATE TABLE MyTable (
MyIndexNum Integer Identity(1,1),
MyText Varchar(40),
MyNum Integer
blah....)
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
schmir1Author Commented:
So I would have to "CREATE TABLE MyNewTable" then do the "SELECT * INTO MyNewTable FROM MyOldTable".
0
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

Jim P.Commented:
You can do a straight Select * Into, but you lose the primary keys, identity fields, etc.

It depends on what you are trying to do.
0
schmir1Author Commented:
I'm still not sure I'm following.  I would like to maintain the primary keys, idendtity fields, etc.  Can you give me an example of how to copy the table and all the data in it to another table and have them both have identical data structures?
0
Gustav BrockCIOCommented:
You would need a tool for that. Access has an "upgrade" wizard for moving tables from Access to SQL Server but not the other way.

Try DeZign:

http://www.datanamic.com/dezign/index.html

<quote>
Supported Databases
Oracle, MS SQL Server, MySQL, IBM DB2, Firebird, InterBase, MS Access, PostgreSQL, Paradox, dBase, Pervasive, Informix, Clipper, Foxpro, Sybase, SQLite, ElevateDB, NexusDB, DBISAM More.
</quote>

/gustav
0
schmir1Author Commented:
This is something that I need to run in my code.
0
jefftwilleyCommented:
is it linked into your Access Database?

You could give the CopyObject method a go

DoCmd.CopyObject, "Employees Copy", acTable, "Employees"


J
0
Jim P.Commented:
>> You could give the CopyObject method a go

The issue is he wants a copy of the original table -- including structure in the BE. The CopyObject just refers to a newly named front end link.
0
schmir1Author Commented:
Jimpen is exactly right.  I need something that runs on the SQL Server but I kick off with my VBA.  Here is basically what the code needs to do:

1) I already have code that "INSERTS" the new data into "Commitment_Outlook_bak"

2) If successful then I need code to copy  Table "Commitment_Outlook" to Table "Commitment_Outlook_sav"

3) If this is successful then copy Table "Commitment_Outlook_bak" to "Comitment_Outlook"

Would it be hard to make a stored procedure and run it from my code.   Could I do a stored procedure that copies directly into "Commitment_Outlook" and roll back if there is a failure?
0
schmir1Author Commented:
I don't think my Stored Procedure idea is going to work.  I just remembered that the table that I'm getting the data from is a Outlook Address list that is resident on my C drive.
0
Gustav BrockCIOCommented:
If so, you can just use

DoCmd.TransferDatabase ...

Look up the on-line help for the full syntax and options.

Use acImport and acTable and study the example for how to include your connection string (which you can look up by linking the table and view the properties of the link table).

/gustav
0
schmir1Author Commented:
I don't think the DoCmd.TransferDatabase is going to work?  

I think I've found a way.  See code below.

If there is no other input then I'll close this question.
Function CreateSPT(SPTQueryName As String, strSQL As String)
'Generate a Pass-Through query then run it
'Params: SPTQueryName - name of the query (will be deleted and recreated if exists),
'        strSQL - query to run on SQL Server include Stored Procedures (Using EXEC)
'Example 1: CreateSPT ("Test", "Select * from Users")  'creates a Pass-Through Query called test with the "Select..." statement
'Example 2: CreateSPT("Generic_SPT", "EXEC RenameTBL ""Commitment_Outlook_bak"",""Commitment_Outlook_bak1""")
'Example 2: CreateSPT ("Generic_SPT", "EXEC sp_rename ""Commitment_Outlook_bak1"",""Commitment_Outlook_bak""")  'using system SP
 
  Dim cat As ADOX.Catalog
  Dim cmd As ADODB.Command
 
  DoCmd.Close acQuery, SPTQueryName
  On Error Resume Next
  DoCmd.DeleteObject acQuery, SPTQueryName
  On Error GoTo 0
  Set cat = New ADOX.Catalog
  Set cmd = New ADODB.Command
  cat.ActiveConnection = CurrentProject.Connection
  Set cmd.ActiveConnection = cat.ActiveConnection
  cmd.CommandText = strSQL
  cmd.Properties("Jet OLEDB:ODBC Pass-Through Statement") = True
'  cmd.Properties("Return Records") = bolReturnRecords  'no worky but On Error Resume Next stopped the error
  cmd.Properties("Jet OLEDB:Pass Through Query Connect String") = _
       "ODBC;DSN=DTLData_Dev;database=DTLData;UID=sa;PWD=;"
  cat.Procedures.Append SPTQueryName, cmd
  DoCmd.OpenQuery SPTQueryName
 
  Set cat = Nothing
  Set cmd = Nothing
End Function

Open in new window

0
Jim P.Commented:
That looks to be the best solution.

Sorry we couldn't give you a better answer.
0
schmir1Author Commented:
All good info although I found what I think is a good solution.  Thanks for your help.
0
Jim P.Commented:
Glad to be of assistance. May all your days get brighter and brighter.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.