2 versions of Access conflict issue

[russi]

Hi.
In our offices, staff have used a vital database coded in Access 97. It is a split one with the datafile stored on a central server and staff in multiple locations accessing it and adding to it via front-ends on their local computers.
Now, they have added Access 2003 to the staff computers and even though they still have Access 97, and the shortcuts to the database are Access 97, staff frequently find they go to the shortcut and get the Access 2003 offer of wanting to convert data.

Due to 'add-on' and other coding we once had a major problem when folks got to the database through access 2003.

So how do i ensure that only Access 97 is used for the database. And why does the shortcut periodically revert to the Access 2003 instead of Access 97?


Russ

 

[KenHigg]

Is the MS Access 97 executable located in the same place (folder) on every machine?

(Somethig like c:\myprograms\msoffice\msaccess.exe)

 

[russi]

From what I understand, the answer is 'Yes'.

Russ

 

[KenHigg]

In that case one idea would be so create a shortcut for the users that opens the correct executable and has the mdb file as a command line parameter.

 

[Len Boorman]

The alternative is to use a 97 backend. 97, 2000 and 2003 FE's all linked to the common 97 BE

Shortct to use whatever version they have and all okay

L

 

[russi]

Hi.
The database is split and the backend is and always has been a 97 one.
And the problem still exits.

Also the desktop icon idea also does not work. Although I will go back and see if there is any other tweaking that I can do.

I do appreciate the ideas and efforts!

Russ

 

[gemma-the-husky]

what access does is tries to open the database using the last used version of access

now, A97 opens an A97 database, but not an A2003 database

BUT A2003 opens both, and will offer to cnovert the A97 database. If you reject the convert, then some things (make tables? i'm not sure) cannot be done in a non-converted database

Hence if users are switching between versions of access, this is likely to explain why they are occasionally using the wrong Access version.

there are utilities that determine which version of access ought to be used, and react accordingly - or you can, as suggested create a pif file to include the correct opening information (and indicate mdw file if necessary)

as long as the dastabase is split properly, you shouldnt get issues, even if some users decide to convert A97 stuff to A2003.