database has been opened read only

[allen davidson]

Hi - I have an .ade file that I think I created in Access 2003 from an .adp.
I am opening it with Access 2007. The database links through to a back end
SQL DB. The .ade is used by many users. When I open the DB I get the message
'this database has been opened read-only. You can only change data in linked
tables. To make design changes, save a copy of the database.' The message
(which seems to have started appearing only recently) confuses both me and
the users. Data can be changed - as carefull reading of the message
indicates. Any idea on how stop the message?

Thanks
Allen

 

[Tom van Stiphout]

On Wed, 27 May 2009 06:56:02 -0700, allen davidson

Not really, but it appears you are running in a bad configuration: the
..ade file should be on every workstation, not on the server. There are
tools such as the one from Tony Toews that can help keep everyone on
the latest version.

-Tom.
Microsoft Access MVP

 

[allen davidson]

Thanks Tom,

Looks like I have the setup all wrong. Is there a way of avoiding having to
distribute any files, we have 200 desktops.

Can I share the .adp on the server?

Regards
Allen

 

[Ron2006]

Not that I am aware of unless you want to make 200 versions on the
server.

The FE should be on the local computer. As stated:
"There are
tools such as the one from Tony Toews that can help keep everyone on
the latest version.
"
Instead of a shortcut to the executable on each computer there would
be a shortcut to the tool and everything would be automatic. For all
practical purposes, the user can't tell the difference. Only if the
version changed would there even be any change in the way it would
appear to execute.

Sharing it on the server will at a minimum lead to the message you are
getting and it goes downhill from there quite quickly.

If it is worth doing, it is worth doing it the right way.

 

[allen davidson]

Thanks Tom & Ron. Guess I'm going to have to do it properly! Thanks also for
the pointer to Tony Toews site.

Cheers
Allen

 

[Larry Linson]

Making changes to a database that others are using in production is a recipe
for disaster; that is why all versions of Access including and after Access
2000 have required that exclusive use is required to make changes in design
view. Changes that can be made to an .ade, in any case, are limited... by
design... so you should not be surprised that you can't modify the database.

Even if you were to disregard the excellent advice that each user should
have his/her own copy of that front-end database, you should be making
design changes on a development copy (.adp), compiling to .ade, and rolling
the .ade out to users only when you have completed and thoroughly tested
your changes.

Larry Linson
Microsoft Office Access MVP