[AccessD] Read-Only error message opening database

John Colby jcolby at colbyconsulting.com
Wed Nov 5 20:20:52 CST 2003


Although according to Gustav I think it was, running it under "run time"
will prevent the error from showing.

John W. Colby
www.colbyconsulting.com

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Charlotte
Foust
Sent: Wednesday, November 05, 2003 9:15 PM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] Read-Only error message opening database


Design changes (like the paper size of a report) are handled in Access,
not in SQL Server.  Access 2000 and later do NOT allow users to make
design changes to objects unless they have exclusive access to the
database.  Since your database is being shared,  that would only be
possible if a single user was in the database.  Also, read-only access
to that folder won't work because the users need to be able to create
and/or write to the ldb file for the shared front end and to delete it
when the last person exits.

Charlotte Foust

-----Original Message-----
From: access at tlcbc.com.au [mailto:access at tlcbc.com.au]
Sent: Wednesday, November 05, 2003 6:03 PM
To: accessd at databaseadvisors.com
Subject: [AccessD] Read-Only error message opening database



Hi!

I have just found this list so apologies if this question has been asked
before
(couldn't see it in the archives).

We have a database that is stored on a shared network drive with the
data
itself in an SQL Server backend.  For security reasons the majority of
users
have read-only access to the network drive where the database is stored.
With
Access 97 this worked fine but the database has recently been upgraded
to
Access 2000 and now the users receive a message when they open the
database
stating that it is read-only so they won't be able to save their changes
(which
is incorrect as, of course, the updates are done on the SQL server which
they
do have write access to).  Not a major problem but very annoying and
confusing
for the users.

Does anyone know how to disable this error message under Access 2000?

Thanks,
Terry Bradford
(Canberra, Australia)


_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com





More information about the AccessD mailing list