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 bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

MS Access version problem

Status
Not open for further replies.

DerekSully

Programmer
Oct 29, 2001
6
GB
I have moved some software on from W97 to W2000. My W97 users cannot now read their W97 databases. My workround (unacceptable) is to have two versions of the software one compiled on a W95 PC where the VB "Reference" is to a version of MS Access 97 drivers, one compiled on a W2k system with with Access 2000 and a different reference in VB. Is there any way of making both Access versions accessible to a VB program where the "Reference" is to Access 2000?

TIA

Derek Sully, London
 
Hi

a bit confused but I'll try and help. Are you saying that you have two version of your database (97 and 2000) with the same vb program connecting to both? And that you have some users running office97 and others office2000?

Kate
 
Hi Kate

Thank you for taking the time. I have a piece of software which is fairly widely used and some of the users look up suppier names on an Access database ... others look them up on SQL Server

Some recent new users have Access 2000 so I upgraded my own systems but some of the older users still use Access 97. I am looking to have one set of VB code and I am happy to have a flag for each user to say that they use Oracle, Access97 Access2k etc

At the moment I am moving the source code backwards and forwards between two PCs ... which is a recipe for disaster! When I call in the VB program on W2k the Project Reference is to MS Access 10.0 Object Library but on W95 it is to 8.0 or 9.0 I cannot remember which.

Hope this clarifies the problem, Derek Sully
 
Hello

Ok, here I go again. this is how I undertand the situation.

You have a number of instances of this s/w running on local machines, connected to a *local* copy of the database (which might be 97/2000/sql).

Question 1
Who set up the original database - is the user given the empty structure or did the vb program actually create this database?

Question 2
Is this database used by another program except for your vb front end?

Question 3
Is the database always local and accessed by only one user?

Question 4
In relation to the same user, does the VB program always connect to the same database?

Possible Solution
Would it be possible to check the version of the database and then amend the provider within the connection string?
In this way, you'd be able to use the same vb for all, as long as the structure of the database is the same for each version.

Kate

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top