Using automation with Access 2002 causes reset default to ver. 200

B

bmutch

I am using automation to open an Access database from VB6. I want the user to have be able to use the app if they have Access 2000 or greater installed. What is the best way to open the Access DB? Currently I am using late binding in an effort to let the computer decide which version to use to open it up, so I am not including a reference in the VB project and I open the db using:
Set objAccess = CreateObject("Access.Application")
On my computer this always seems to use Access 2000 ( I have both 2000 and 2002 installed). Even when I make Access 2002 the default version on my machine by running Access 2002 directly, when I then run the CreateObject statement above, the Office 2000 Installer runs and sets the machine back to making Access 2000 the default. Why is this happenning and what is the best way for me to use automation so that it will work with Access 2000 or greater installed.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Execute Procedure on a remote Access Db file 17
Active X component can't create object Access.9 3
script to compact database VBS 14
Printing an Access report using late binding 7
Cannot Convert Access 2002 DB To Access 2007 6
Opening another DB from a DB 1
Deploying Access 2002 Runtime 4
Access VBA to open Excel workbook, save as a dbf (I think) 5

Top