adodb connection error

Question

Hi, I'm the database person at a big company. I built a few MS Access databases which staff use daily. The company was still on XP and some of the computers still are. Some have been upgraded to windows 7 with ms office 2010. The database was still working fine. Last week some of the computers were upgraded to windows 7 with ms office 2013, now my access programs are broken. We tried to uninstall office 2013 and install office 2010, but this did not solve the problem. It chokes where I set my adodb connection like: set MyVar = new adodb.connection. The error is -2147024769 (8007007f) Automation error. The specified procedure could not be found. Can you please help, I'm desperate! We've tried quite a few things already, but nothing is working so far. THanks

Answer 1

Hi Tom, Sorry I did not check back until now, I much appreciate your answer.

> Funny enough it is able to read

That does not surprise me. The "Dim" line only announces that there will be a variable of that type. The "New" line actually creates an object of that type.

I'm not sure I agree with your statement. If I don't have the correct libraries attached, it will give me a user defined error right on the Dim line. So, all I was really referring to, was that I had the correct libraries attached.

I tried many things, also other ways to connect, however, the same database is working on 50+ other computers, only on a select number it did not work after upgrading to windows 7. In the long run we decided to re image those machines and that did take care of the issue.

Again, thank you so much for your help!

Answer 2

> Funny enough it is able to read

That does not surprise me. The "Dim" line only announces that there will be a variable of that type. The "New" line actually creates an object of that type.

You can try CreateObject, and it will fail as well, but maybe, just maybe the error message may be more informative.

You can also see about upgrading ADO somehow. Maybe there are updates available that have not yet been applied.

Or maybe you can switch to using DAO?

Last resort would be to conclude that these computers were built incorrectly or using a faulty image. Wipe one clean and reinstall from scratch.

Answer 3

Also, it happens with any instance of Access, I've tried Access 2003/2007/2010 as well as 2013

If anyone can help me with who to ask it will be helpful too. Thanks!

Answer 4

Hi Tom, thank you for answering. I've tried everything you describe there, I even opened a new database with only the adodb connection declaration and setting. Funny enough it is able to read the dim CNN as adodb.connection, but it chokes on set CNN = new adodb.connection. It is almost as if something other than the database is stopping it. The same database is working on all the computers with xp and windows 7, it is only those ones that were distributed on one day last week that has the problem, unfortunately it is a large number of computers! There are around 60 users and about 40 computers are affected.

Answer 5

For testing, use the accdb rather than accde.

Decompile the application.

Ensure there are no broken references.