Access 97 Runtime with Access 2000 installed

[Jason]

Hi,

We have distributed some Access 97 runtime databases to end users as front
end. The backend is located at the File Server.

Recently, their machines get Access 2000 installed for other purposes.

We would like to know when they open the Access 97 runtime databases, will
they be asked for converting it to Access 2000 format ? If YES, and they
press YES, will the runtime still works for them ? Is there any problem if
the front end is Access 97 and the backend is still running Access 97 ?

We only have the Access 97 ODE but without ODE for Access 2000 / 2003.
Should we purchase a copy of the ODE ? If YES, which version should we
purchase ?

Thanks

 

[Arvin Meyer [MVP]]

Answers in-line:

Hi,

We have distributed some Access 97 runtime databases to end users as front
end. The backend is located at the File Server.

Recently, their machines get Access 2000 installed for other purposes.

We would like to know when they open the Access 97 runtime databases, will
they be asked for converting it to Access 2000 format ?
Yes

If YES, and they
press YES, will the runtime still works for them ?
No

Is there any problem if
the front end is Access 97 and the backend is still running Access 97 ?

I think you mean front-end running the later version (2000/2003) and the
back-end running the older version (97). Yes, you can do that.

We only have the Access 97 ODE but without ODE for Access 2000 / 2003.
Should we purchase a copy of the ODE ? If YES, which version should we
purchase ?

If you want runtimes with the later version, you'll need to purchase the
tools to make them.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads
http://www.datastrat.com
http://www.mvps.org/access

 

[Rick Brandt]

Hi,

We have distributed some Access 97 runtime databases to end users as
front end. The backend is located at the File Server.

Recently, their machines get Access 2000 installed for other purposes.

We would like to know when they open the Access 97 runtime databases,
will they be asked for converting it to Access 2000 format ?

Depends. In all of the runtimes I have distributed the shortcut that I created
with the installer always explicilty included the path to the runtime executable
then the file to open. A shortcut like that will not be affected by another
version of Access being installed on the PC. If your shortcuts merely point to
the MDB/MDE file then yes, using them after installing Access 2000 will cause
Windows to attempt to open them with Access 2000. If the file is an MDE the
user will be asked if they want to convert them, but the conversion will fail if
attempted anyway.

If YES,
and they press YES, will the runtime still works for them ? Is there
any problem if the front end is Access 97 and the backend is still
running Access 97 ?
We only have the Access 97 ODE but without ODE for Access 2000 / 2003.
Should we purchase a copy of the ODE ? If YES, which version should
we purchase ?

If you have already set up your shortcuts properly or can fix them then you
should not have any problems with YOUR apps. However; the user will have to
deal with some issues with their own use of Access 2000.

When you have more than one version of Access on a machine each one that is
launched will register itself as the file to use for all MD? files. So if the
user launches your runtime app and then later double-clicks one of their own
version 2000 files the system will likely attempt to open that file with the 97
runtime. This will obviously fail.

Basically on a PC with multiple versions of Access you have to abandon the
practice of opening files by double-clicking. You need to open the desired
version of Access first and then open the desired file from within. If they do
that then the two versions will "get along" fairly well. I have 97, 2000, 2002,
and 2003 on my work PC and have no problems.

 

[david epsom dot com dot au]

If you remove Open Exclusive permission, they won't be
able to convert the database.

If you change the file extension from .mdb to .dat, they
won't get Access 2000 when they double click, and will be
forced to use the correct shortcut.

If you empty out the file MSACCESS.SRG, Access 97
runtime won't grab the .mdb file association away from
Access 2000, and won't try to re-register when run
after running Access 2000.

Don't get the Access 2000 ODE (which you can't get
anyway). If they already have Access 2000 installed,
you don't have to provide the runtime, do you? You
can still use the A97 ODE to build an installation
with an A2000 database without the runtime, or you
can get a different install tool to build a modern
installation package without the runtime.

(david)

 

[Jason]

Thank you for reply from all of you.

The database distributed to them is only in MDB format (Not MDE). In this
way, I believe that they will be asked to convert the database.

I believe that if it is converted, the worst scenario is just remove the
Access 97 runtime & leave the front end MDB for accessing the backend data
at the Server. Is it correct ?

Thanks again.

 

[Rick Brandt]

Thank you for reply from all of you.

The database distributed to them is only in MDB format (Not MDE). In
this way, I believe that they will be asked to convert the database.

I believe that if it is converted, the worst scenario is just remove
the Access 97 runtime & leave the front end MDB for accessing the
backend data at the Server. Is it correct ?

Assuming that it converts properly, yes.

 

[Guest]

I believe that if it is converted, the worst scenario is just remove the

The worst case scenario is that the converted application runs
slowly and frequently corrupts the BE database.

But that's a worst case scenario.

Clients who don't have admin permission on their own PC's
ie fully locked corporate Standard Operating Environment,
may be locked out of A97 after running A2000 if you haven't
emptied out MSACCESS.srg. Which can cause confusion and
distress. If you don't plan to use A97, you should not install it.

(david)

 

[Jason]

Dear David,

You are right. I should uninstall the runtime and just converted the front
end database.

Thanks