Access 2000 Application with Access 97 Installed

[Roger Lee]

We are still using Access 97 at our site and Access 97 is
installed on each workstation.

However, recently, the developer of an application says
that the app is developed by Access 2000 & we have to get
Access 2000 installed (So that we can run his app).

At the present moment, end users access a couple of Access
97 Databases that will not be converted to Access 2000 in
the near future.

Should I ask the developer whether end users can install
Access 2000 runtime version (So that his application can
be run) and keep Access 97 on users' workstations so that
they can still use the Access 97 databases.

The reason for not installing Access 2000 on those
machines is because we may attempt to convert those Access
97 databases when they open it with Access 2000. In this
way, users in other sections will have problem in opening
them.

However, from newsgroups, it seems that there are a lot of
problems for the co-existence of both Access 2000 runtime
cum Access 97.

I would like to seek your advice on the best way to handle
it.

 

[david epsom dot com dot au]

1) Make sure each copy of Access 97 is on Service
Pack 2, Release 3: it is difficult to apply the
Office 97 Service pack after Office 2000 is installed.

2) Create a shortcut to Access 97 for each Access 97
application that you have.

3) Delete all or most of the contents of MSAccess.srg

4) Make this registry change:
ACC2000: How to Suppress the Convert/Open Database Dialog Box
http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q275164

That should cover most eventualities.
(david)

 

[chriske911]

tell the developper to build two versions of a front, one fro '97 and one
for 2k, use a clearcut naming convention to keep track
access '97 back end (data only) can be used by '97 and 2k and XP fronts
without problems whatsoever

bon chance