-2147024769 Automation error The specified procedure could not be foun

[Stasky]

When trying to open a recordset in Access VBA we get the error:

"-2147024769 Automation error The specified procedure could not be found"

This only occurs on one PC where upto 30 other PCs work fine with the same code.

I think it is something to do with the MDAC installation but re-installing does not seem to fix it.

Our code is:

Dim rst As ADODB.Recordset
Set rst = New ADODB.Recordset
rst.Open "dbo_Table1", CurrentProject.Connection,
adOpenKeyset, adLockOptimistic, adCmdTableDirect

It fails on the "Set rst".

Any suggestions welcome

 

[PaulBricker]

I googled "-2147024769 Automation error" and found a post that had some of the same issues you are facing. The post made a reference to the wshom.ocx file. You might check the offending machine to see if that file is present.


Paul

 

[Stasky]

Paul

wshom.ocx seems to be on all computers.

Only this one does not work.

I think it is something to do with the registration of the ADO DB files into the GAC. The system worked fine until IT update the system nd a number of these files were replaced.

I have tried reregistering the msado21.tbl but no differance. Not sure if I need to delete the ADOdb entry in the GAC first and if I do what else it will affect.

Stasky

 

[PaulBricker]

All I can do to help is google some of the keywords that you are running into. I googled "ADO DB files into the GAC" and found this.

http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=221287&SiteID=17

I make no claims to whether it will help, but there is some food for thought here.

Paul

 

[JoeAtWork]

Automation error" is kind of a generic error so Google searches will probably be more misleading than anything else.

Basically, something isn't installed correctly on your system. And I think you are on the correct assumption that it has something to do with MDAC.

I would start by checking for missing references on the problem machine.

 

[malcolm45]

Paul's link to TechNet looks like a possible solution. I will give it a try

Stasky