troubleshooting of Access runtime error class not registered

[Guest]

After a recent upgrade of Windows 2000 to XP the swicthboard of two access
2003 databases will no longer open correctly. The error message given is a
Microsoft Visual Basic Run-time error '-2147221164 (80040154)': Class not
registered
I have tried removing office completely using, uninstall, then the removal
wizard, then cleaned the registry using reg mechanic. The error persists
after the base installation w/o updates or patches and remains through all
patches to the latest rev MS Access 11.6566.8107. I have attempted searches
on all or part of the message with nothing notable.
Any ideas of where to start to resolve the issue?

 

[Guest]

Hi Thane,

Try re-registering the Msado15.dll file. Click on Start > Run. Then enter
the command:

Regsvr32 "C:\Program Files\Common Files\system\ado\Msado15.dll"

Just for good measure, do the same thing with your DAO360 file (it won't
hurt anything to re-register a file that is correctly registered):

Regsvr32 "C:\Program Files\Common Files\Microsoft Shared\DAO\Dao360.dll"


If your copies of Msado15.dll and/or Dao360.dll are in different folders,
then make the necessary adjustments to the paths indicated above. Make sure
to include quotes around the paths.


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

 

[Guest]

Tom, Thank you!
Although your instructions didnt resolve the problem at first go, I followed
through and re-registered every other darn .dll in those two directories. (A
total of 7 others) And although I was sloppy and didnt do them one at a time
so I know which one, overall it worked when I was finished.

Briefly is there something that send you in the direction of a dll register
issue?

 

[Guest]

Hi Thane,

Excellent. Good to hear. I am kind of surprised that the first registration
attempt did not solve the problem, but stranger things do happen.

Briefly is there something that send you in the direction of a dll register
issue?

Yes. You mentioned switchboard and Run-time error '-2147221164 (80040154)'
in the same paragraph. Starting with Access 2000, switchboards created using
the Switchboard Manager use late bound (no checked reference required) ADO
code. I guess I've just seen that run-time error so many times over the
years, that I immediately think ADO problem. The easiest fix to attempt first
is to re-register the ADO library, which is done with the command I gave you.
If that had not worked, then I would have pointed you to the MDAC (Microsoft
Data Access Components) Checker utility, which you can download from
Microsoft to test the integrity of your ADO installation. Here is a link to
this utility, if you'd like to become familiar with it:

Component Checker: Diagnose problems and reconfigure MDAC installations
http://support.microsoft.com/?id=307255

Personally, I do not care too much for wizard created switchboards. If this
is the only place in your code that you are using ADO, then my suggestion is
to simply use an unbound (ie. no record source) form to create your own
switchboard. You can use the command button wizard to add command buttons.
Sometimes it's nice to add a tab control, to help segregate various buttons
into logical groups. If you use this technique, set the visible property for
the record selector and navigation buttons to No, since the form is unbound.
Set scroll bars to None. You might even want to set the border style to
dialog, to prevent the switchboard form from being resized.


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________