Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Wanet Telecoms Ltd on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

opening access database

Status
Not open for further replies.

gagirl43

Programmer
Nov 3, 2004
8
US
I'm having some bizarre problems with a VB6 program that opens an Access database. The database was originally a 97 version. I converted it to 2000, made necessary changes to to the code and tested it. Everything worked fine. Now I copied the production database into my test area, converted it, changed the code to point to the production drive and moved everything to the production drive. Now when I try to display a record, I get an "unrecognizable database" error. When I click OK, it displays the record without any problem. I tried creating a new 2000 database and copying the converted files into it just to see. Same problem. Then I decided to rename the database and changed the VB code accordingly. I created a new exe and moved it to the production drive. Now I get the message that it can't find the old database name. I get the same message with my test exe which is on a separate drive. I am totally confused. Any help will be greatly appreciated.

 
Instead of just "copying" the EXE file to the production server, have you tried "uninstalling" the previous app and the "re-installing" the new app after you create the new installation package (via PDW or others). This should bring with it the Jet DLL file(s) necessary for 2000.

"Life is full of learning, and then there is wisdom"
 
Maybe you have an ADO Connection String in a constant somewhere else in your code?

Maybe you are using an old DSN that still has the old name?

Reinstalling might help something but that doesn't explain why you are seeing the old database name.
 
Thanks for the help. I ended up creating a separate folder for the 2000 database then naming the database and .exe something different. (Making the code changes of course.) That seems to have worked....don't ask me why.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top