Looking for CLSID .... error

[bcyde]

I am getting an error for my app after running the setup on certain computers. The program gives the error Looking for object with CLSID: {....}. I have traced the error to parts of the program that use databases. All of the databases are using normal data controls. The databases were created by the visual data manger in Visual Basic and compacted as a 7.0 mdb. I was wondering if there were any necessary references I need to add to the project or is it just that I am not initializing the databases correctly? The error only occurs on certain computers, I believe ones that do not have Microsoft Access installed. When I first load up the main form I initialize the data controls in this manner:
Data1.DatabaseName = App.path & "\" & USER & "\apm.mdb"
Data1.RecordSource = "keytable"
Data2.DatabaseName = App.path & "\" & USER & "\gk.mdb"
Data2.RecordSource = "gatekeeper"
during the form load event
Hope this info helps. Thanks in advance.

[shanep]

Did you try searching for the class ID in the registry? One of the data access controls/dlls may not be registered. You may have to run the MDAC install on them if the problem persists.

[bcyde]

I have checked the registry for the computers that I have been installing the program on and have not been able to find that key in the registry. The CLSID I'm looking for is:
{00000010-0000-0010-8000-00AA006D2Ea4}
and the closest thing I find on all the computers (including the ones that the app won't work on is:
{00000507-0000-0010-8000-00AA006D2Ea4}
which is found in H_key_class_root->ADODB.Command->CLSID
Does this mean anything to anyone? Thanks for your previous post. Also I tried looking through the code in a text editor looking for all instances of the key or any place that it says object, but I still can't find it. It seems really strange and is quite frustrating. =(

[shanep]

I searched for that CLSID in my registry, and it's the dao350.dll. It should be in the Microsoft Shared\DAO directory.

Does your install program handle the registering of the dlls? Have you doublechecked everything in MSDN Article ID: Q167523?

I once had a similar problem but with ADO components. When we shipped, the install guys compained about the install program locking up. Installing the ADO components failed, I guess. Out of desperation, I just ran the MDAC install and everything was smooth sailing. I don't think MDAC will fix this this, but I believe Microsoft Office 97 SR2 updates that DLL.

[bcyde]

Thanks for searching your registry, I was actually able to fix the problem right before reading your response, but thanks for taking the time to help out. At least now I know what the CLSID was. Thanks again...