No references marked as missing. Only four are checked 1. VB for Applications, 2. Microsoft Access 10.0 Object liabrary 3. OLE Automation and 4. Microsoft DAO 3.6 Object Library.
Main Topics
Browse All TopicsI have a simple Access contacts data base that I have used for years. It began as an Access 97 Contacts Template and I have made many additions since then. It uses a switchboard to control contact searches and report queries. Searches are driven by 2 simple combo boxes tied to search/match queries; one for contacts and one for client names.
The program was begun with Windows 2000 / Access 97 and was eventually upgraded to Access 2002 several years ago; everything working fine.
Three weeks ago I began using a different laptop with Windows XP and Office 2003 and transferred my database. After this change, when I attempt to search for a contact or a client using either combo box, I now get an error message in a Microsoft Visual Basic message box: Run-time error 429: ActiveX component cant create object. The error message gives me options to End or Debug.
When I start to debug, the code line in yellow is: Me.RecordsetClone.FindFirs
Steps I have taken:
I sent the database to another computer also with Windows XP and Office 2003 and the data base Combo boxes work as designed.
I uninstalled Office 2003 and reinstalled a totally different copy of Office 2003 no change, still the same error messages.
I uninstalled Office 2003 reinstalled my old Office XP -Access 2002 no change, still the same error messages.
I have registered the DAO350.DLL using regsvr32 "C:\Program Files\Common Files\Microsoft Shared\DAO\DAO350.DLL successfully, as mentioned in another solution on this website no change, still the same error messages.
I have deleted the combo boxes and attempted to rebuild new boxes and get the following Microsoft Access Message Box error message: ActiveX Component cant create object.
Every other part of the database works fine and all the switchboard command buttons work correctly. All queries work and all reports print correctly. My only issue is with the two search combo boxes.
Any suggestions would be appreciated.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
TaeSoft:
At the risk of showing my lack of knowledge -- This data base worked on Win2000/Access 2002, then on XP/Office 2003 I started getting the error message, I uninstalled the Office 2003, reinstalled my old Office XP 2002 as before and now I have the same error message. Seems like it has to be an issue with WinXP or VB6?
r58
Dear rlindsay58,
I've struggled a lot with Access too in the past. But I think your problem lies with ocx.
I think the combo's you are using are obsolete in the newer version.
Can you reinstall the old ocx for these comoboxes?
In the other case,
if you are out of time,
I would delete the combos in all the forms and re-create them with the latest versions.
I think VB6 doesn't have anything to do with it.
I hope it helps.
Kind regards,
TaeSoft
Correction about the VB6,
Maybe you've used an ocx comming from VB6 that is now not installed anymore and you need to have it.
But to be sure:
- Check the old accessfile to see what kind of control the combo is.
- Look up with which dll this activeX is installed and install it on your new pc.
Kind regards,
TaeSoft.
TaeSoft:
I failed to mention that when I transfer the data base to other computers also using WinXP and Office 2003, the combo boxes work fine. The problem, it seems, is limited to just my laptop??? I have tried to rebuild the combo boxes and get the error message that "ActiveX component cannot create object".
When I get a chance I will try Steve's suggestion of unchecking the DAO and then rebuilding.
Thanks for all your suggestions; I appreciate you advice.
r58
The references checked on the computer where the database works correctly are the same as the references checked on my laptop. The "only difference" is the working computer refers to Microsoft Access 11.0 Object library (this computer has Access 2003) and my laptop refers to Library 10.0 (using Access 2002 currently).
When I tried Steve's suggestion and unchecked the DAO (identified as DAO 3.6) my laptop rebuild DAO 3.5 (DAO 3.6 no longer listed) and still the same error message.
TaeSoft:
I am pretty certain I have VB 6 because it is located in my Win Directory identified as VB6.
I need help on your suggestion -- "Maybe you've used an ocx comming from VB6 that is now not installed anymore and you need to have it.
But to be sure:
- Check the old accessfile to see what kind of control the combo is.
- Look up with which dll this activeX is installed and install it on your new pc."
How do I identify the type of control my combo box is? Sorry for a stupid question??? Once I Identify the type of control, how do I check "which dll the activeX is installed etc.....
r58
I have solved my problem. I split the points between all who steered me to the references as being my problem. None of the suggestions were exactly correct but all were close. What I did was uncheck DAO 3.6 in the references, then "browsed" to DAO 3.6 in the Microsoft Shared Folder in Common Files and selected DAO 3.6. That solved the problem, must have been some type of disconnect between the Shared Folder and References.
Thanks ALL for your suggestions.
r58
Business Accounts
Answer for Membership
by: mbizupPosted on 2007-07-19 at 13:00:52ID: 19525578
On the computer that is having this issue, check the references:
- Open the VBA Editor in Access
- From the toolbar menu: Tools -> references
- If any references are labeled MISSING, uncheck them, then search the list for the most current version of the reference and check that.
- Click OK to save and close