Access 97 & 2000 on shared network question..

lord of the badgers

Board Regular
Joined
Jun 17, 2003
Messages
208
at work we have the following suggestion
As you know, one of the concerns over MS Access is the possibility of a user on W2K opening an Access 97 database, encountering the "do you want to convert this DB" message, then logging a helpdesk call, or attempting to convert the database anyway. Although the latter would not damage the original database, in a multi-user case it raises the possibility of data loss through having duplicate copies of the same database.

Up to now, we've accepted that this "convert dialog" message can't be suppressed, and we'd need to manage it through comms or redesign. This was based on a statement from the Microsoft Access 2000 website. However, in the course of some work Monday it's come to light that this is wrong. In fact there is a registry key which can suppress the message. This key is user-based, so it would apply to a given user whichever PC they were on.

With the key set, a user on a W2K PC opening an Access 97 database sees the following:

The database opens normally, with no messages

Data entry and browsing work normally

Icons which perform design changes, as opposed to data changes, are greyed out. So, for example, if you browse the window listing all the forms the "delete" icon is greyed.

Opening a form or table in design view is possible, but changes are ignored

If user persists in trying to change the database's design, there is a longer message which gives instructions how to convert (i.e. close the DB, go to Tools, Database Utilities, Convert Database).

is there any other thing we could use (ie an add-in) which might have a favourable answer - ideas?
 

Excel Facts

Round to nearest half hour?
Use =MROUND(A2,"0:30") to round to nearest half hour. Use =CEILING(A2,"0:30") to round to next half hour.
I cant help with suppressing the Msg but judging by this quote
, in a multi-user case it raises the possibility of data loss through having duplicate copies of the same database.
You have not split you DB into a front End / Back End configuration. Split dadabases are advisable as most corruption occurs in the front end which can easily be repaced by a backup

Peter
 
Upvote 0
yes we have many examples of split dbases (inc my own), but in our environment we have to accept that some users haven't done this (it's a big ol company this... about 3000 potential users of many many databases out there)

the email came from the IT support company, and i'm tempted to vote OK on it, but obviously, if there's any other 3rd party thing out there it may be useful...

thanks anyway
 
Upvote 0

Forum statistics

Threads
1,221,572
Messages
6,160,575
Members
451,656
Latest member
SBulinski1975

We've detected that you are using an adblocker.

We have a great community of people providing Excel help here, but the hosting costs are enormous. You can help keep this site running by allowing ads on MrExcel.com.
Allow Ads at MrExcel

Which adblocker are you using?

Disable AdBlock

Follow these easy steps to disable AdBlock

1)Click on the icon in the browser’s toolbar.
2)Click on the icon in the browser’s toolbar.
2)Click on the "Pause on this site" option.
Go back

Disable AdBlock Plus

Follow these easy steps to disable AdBlock Plus

1)Click on the icon in the browser’s toolbar.
2)Click on the toggle to disable it for "mrexcel.com".
Go back

Disable uBlock Origin

Follow these easy steps to disable uBlock Origin

1)Click on the icon in the browser’s toolbar.
2)Click on the "Power" button.
3)Click on the "Refresh" button.
Go back

Disable uBlock

Follow these easy steps to disable uBlock

1)Click on the icon in the browser’s toolbar.
2)Click on the "Power" button.
3)Click on the "Refresh" button.
Go back
Back
Top