• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 415
  • Last Modified:

Multiple step OLE DB error

Hi Experts,
    I have a database that I have been using to compile work reports from 4 sources monthly. The reports come in as .mdb files named with a prefix for the user sending the report, the report name & month the report is for (example: prefix= "KN", report = "chk", month= "Aug" > Filename = "KNchkAug.mdb"). Then inside each file contains a set of tables having a standard set of names except that each tablename begins with the prefix for the user that sent it in like this, KN_Checklist.

    All was working fine until I decided it needed to be improved for timing sake. My front end has a form that I enter the current month and the user to import from and then I was using "DoCmd.TransferDatabase acLink" to update the link to the correct workreport BE, after which I would run append queries to compile the data as needed. Since upgrading to Access 2003 however the "TransferDatabase" method has been noticably slower than it used to be in previous versions (taking up to 3 seconds per linked table). So I decided to look for a better method and this is where my problem arrived. Here is the code I am trying to work with:

'********************************************
Function RefreshLink(newBE As String, newPrefix As String)

    Dim cat As Object
    Dim tbl As Object
    Dim oldNM As String
 
    Set cn = CreateObject("Adodb.Connection")
    Set cat = CreateObject("ADOX.Catalog")
    Set tbl = CreateObject("ADOX.Table")
 
    cat.ActiveConnection = CurrentProject.Connection 'cn
 
    For Each tbl In cat.Tables
        If tbl.Type = "LINK" Then
            'mytbprop = tbl.Properties
            oldNM = tbl.Properties("Jet OLEDB:Remote Table Name")
            oldNM = Right(oldNM, Len(oldNM) - 2)
            With tbl
                .Properties("Jet OLEDB:Remote Table Name") = newPrefix & oldNM
                .Properties("Jet OLEDB:Link Datasource") = newBE
            End With
        End If
    Next
 
Set cat = Nothing
Set tbl = Nothing
 
End Function
'********************************************

when the function hits ".Properties("Jet OLEDB:Remote Table Name") = newPrefix & oldNM" I get the following error:

        Run-time error '2147217887 (80040e21)':
        Multiple step OLE DB opperation generated errors. Check each OLE DB
        status value, if available. No work was done


Any help? I have little time to work on this today, so maximum points.

TIA!

Sam
0
will_scarlet7
Asked:
will_scarlet7
  • 7
  • 5
2 Solutions
 
shanesuebsahakarnCommented:
How about just running an append query without linking to the tables?

INSERT INTO SomeTable SELECT * FROM AnotherTable IN 'C:\SomeOtherDB.mdb'
0
 
will_scarlet7Author Commented:
ThanX for the response shane! I will consider your suggestion, but I am hoping to get the linking resolved. One reason for which is that at current I have the process broken up into steps, so that after linking the data I can preview it before appending it if needed. I know I can work around this by using ADO recordsets, but the link seems like the simplest.
0
 
shanesuebsahakarnCommented:
Does it work if you swap around the Link Datasource and Remote Table Name lines? I'm not terribly familiar with ADOX.
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
will_scarlet7Author Commented:
It causes the same error.
0
 
shanesuebsahakarnCommented:
:( I could tell you how to do with DAO, but I'm not sure if that would be any faster.
0
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
This is one of those "catchall" errors that ADO throws at times ... are you sure you're supplying enough information to the complete the operation? ADOX is pretty fickle about the order of items, and if you try to "set" an object or property without something else already being set, it'll choke on you. Check this link to make sure you're issuing the correct items in the correct order:

http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q240/2/22.ASP&NoWebContent=1
0
 
will_scarlet7Author Commented:
Thank you both, Sane & LSM!

    I think the problem lies in that the ".Properties("Jet OLEDB:Remote Table Name")" must be a read only property once the link is made. So nice of our dear Microsoft to just give generalities in their error message...

    What I opted for was a change in tactic. The code below moves through a recordset to get the old link name and delete it then import a new link to the current BE.

Sub CreateLinkedTableADO(dbBE As String)
   
    Dim cat As Object
    Dim rs As Object
    Dim tbl As Object
    Dim strSQL As String
 
    Set cn = CreateObject("Adodb.Connection")
    Set rs = CreateObject("Adodb.Recordset")
    Set cat = CreateObject("ADOX.Catalog")
    Set tbl = CreateObject("ADOX.Table")
 
    cat.ActiveConnection = CurrentProject.Connection
    strSQL = "SELECT * FROM stpLinkedTables WHERE stpLinkedTables.Category = 'ABM';"
    rs.Open strSQL, CurrentProject.Connection, 2, 1
    rs.MoveFirst
   
    While Not rs.EOF
        DoCmd.DeleteObject acTable, rs("LinkName")
        Set tbl = New ADOX.Table
        Set tbl.ParentCatalog = cat
        With tbl
            .Name = rs("LinkName")
            .Properties("Jet OLEDB:Create Link") = True
            .Properties("Jet OLEDB:Remote Table Name") = rs("TableName")
            .Properties("Jet OLEDB:Link Datasource") = dbBE
        End With
        cat.Tables.Append tbl
        rs.MoveNext
    Wend
   
    rs.Close
    Set rs = Nothing
    Set cat = Nothing
    Set tbl = Nothing

End Sub

Seems to be working good so far (and ten times faster than the TransferDatabase method).

All your help was appreciated. Are you OK if I split the points between you with a grade of "B"? I'd rather do that then have the question PAQ'd since I don't need the points refunded. Let me know your preference.

God bless!

Sam
0
 
shanesuebsahakarnCommented:
> Sane & LSM!

Sane I am not :) It's ok by me, Sam but I'll leave it up to you.
0
 
will_scarlet7Author Commented:
Sorry Shane...
0
 
will_scarlet7Author Commented:
Any chance I can post a second question about the above code (not @ ADO) here and you answer that way I can award an A for the answer? Or should I close this one and open a new one?
0
 
shanesuebsahakarnCommented:
I don't mind either way Sam, so long as I can help :)
0
 
will_scarlet7Author Commented:
I'll close this with a "B" and open a new one (more points available to be earned that way)

ThanX again!

Sam
0
 
will_scarlet7Author Commented:
0

Featured Post

Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

  • 7
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now