Use of an Access 97 database by XP and 97 users

[justin]

Hi, I have encountered a problem with running a multi-
user Access 97 database, and hope someone out there has
the answer. Please help...

I am rolling out a database (together with VB code) to 15
users, some of whom have Access 97, some of whom have
Access XP. To be used by the '97 users, I have to roll it
out as an Access 97 database.

My problem is that whenever XP users open the database,
they are asked if they want to upgrade it to XP.
Occasionally users reply YES, the database is converted
to XP, and is then no longer usable by '97 users.

What I am looking for is an option / flag which in XP
would switch off the option to upgrade. Does anyone have
the answer, or a suggestion as to how else this prblem
might be overcome?

Many thanks in advance,

Justin

 

[John Nurick]

Hi Justin,

The usual technique in this sort of situation is to split the database.
Leave the back end in a shared folder, but put a copy of the front end
on each workstation. This is a good idea for any multi-user Access/Jet
database because it reduces the risk of file corruption, but it also
means that the front ends can be converted to the newer version while
continuing to share the Access 97-format back end.

 

[Chris Mills]

If you are rolling it out with VB code, why is the Access version relevant?

Do you mean they are using both MS-Access and a VB-code front-end.

If they are opening it in VB code, why mention opening it in Access?
Conversely, why mention VB code?

An A97 "BE" can be rolled out with any later version. Of course, only
MS-Access97 can repair/compact it (I understand).

To suppress the later-version question whether to upgrade, I thought this was
suppressed AFTER the FIRST time you so open the database. But that is too
easy, you must be asking something else...

(I take splitting into FE/BE as a given, since you mentioned "together with VB
code". However, even if it was a single database/code, I thought it would
suppress the message after the first "proper running". There is no flag/since
it's automatic if done right)

Chris

 

[Stewart Tanner]

Justin,

you need to open the database in XP and enable it before roll out. This
will prevent the automatic question of Convert / Enable that occurs when the
system is first opened.

This will not stop a user who deliberately goes to tools convert but it will
stop the accidental conversions that you mentioned.

Stewart