Prevent 97 users from converting DB to 2003

[jjonesal]

I currently have users that have both 97 and Access 2003 installed on their machines. We have many databases on the network that users access - some in 97 format & some in 2003 format. When a 2003 user opens a 97 format database, they used to get the Open/Convert dialog - and using the KB article & Group policy, we have supressed that.

However, the user still gets a message indicating that the database is in an older version which gives them instructions on how to convert.

My question is: Does anyone know of a way to PREVENT users from converting (at least until we're ready for them to). We have some Access 97 databases that external users access that must stay in Access 97, and I don't want users taking it upon themselves to convert.

Any suggestions or ideas would be greatly appreciated...

 

[PHV]

A common way is to create shortcuts with the proper msaccess path for each database.

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886

 

[jjonesal]

Thanks - thought about that, but got about 3000 databases & some of which will need to be opened by 2003 and 97 users. Just don't want the 2003 users converting the file format (hence locking out the 97 users)

 

[lameid]

Hmmm... My users don't have exclusive database permission to my files. This means I have to open the database in 2003 with appropriate permissions to let them view the files. On the otherhand they can't convert the files to a higher version. This is of course Jet security. And it would be a dog to implement on that many databases especially considering the only way I know to seize ownership of a database is to import all the objects to a new file. Unless of course the Jet 'Admin' user (default) does not own the databases (doubtful). The other caveat of this method is that any object change will keep the Access 2kX users out until someone with exclusive access reopens the database.

Another alternative would be to buy Visual Studio Tools for the Office System Version 2003 and deploy the runtime to your external users so that they can use the Access 2003 format.

3000 databases... That's one big organization. I'm sorry I don't have an easier answer for you.

 

[alvechurchdata]

We solved the problem by having a standard 97 backend and by having 97 frontends on the 97 PCs and 2003 frontends on the 2003 machines. It sounds as though you've got everything on the server and with 3000 databases that's a lot of work keeping two versions of every front end in synch.

Geoff Franklin

http://www.alvechurchdata.co.uk