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

2 versions of Access

Status
Not open for further replies.

DajOne

Technical User
Joined
Jun 11, 2002
Messages
146
Location
CA
Our company is )slowly) switching from Access 97 to Access 2000. The users of the 97 databases will be switched at different times to 2000...

How can users with different Access versions be able to enter data in the same database until all the users are to Access 20000

 
The most efficient way to effect this requirement is to deploy access 2000 runtime to the persons who still have access 97. This can be done via the Access 2000 Developer edition, which associates the access2000 database to the rune-time instance. There is no extra cost for having the runtime deployed on as many workstations as is needed.
 
Actually, I'd say the best way is to keep all of the back ends in 97 and deal with the pain of one front end in 97 and one in 2000.

Actually, even better than that would be to fire the person who made the decision to roll out a software update that will affect users of the same database over time. This should all happen at once. Period.

Jeremy =============
Jeremy Wallace
Designing, Developing, and Deploying Access Databases Since 1995

Take a look at the Developers' section of the site for some helpful fundamentals.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top