'database is read only' on users machine

[jerryreed]

I've completed some general programming updates on an existing Access 2000 .mdb in a Windows XP environment. The mdb now uses no internal tables -- it links to SQL Server 2000 data. The mdb runs fine from all machines -- users can still work and modify data without problems , however, when users open the mdb, they now receive a message stating that 'The database is read-only."

Security properties for the mdb as set up as Full Control for Admin (myself)
and Read & Execute and Read for all Users.

I've tested giving all Users Full Control (as well as adding the Write permissions) to all users. And while they no longer receive the read only message, the user gets a message stating that the 'database cannot be opened' when exiting the program.

Again, this is an existing mdb which, on previous versions, didn't show the 'database is read only' message with the current security properties for all users set to Read & Execute and Read.
thanks!

 

[willir]

jerryread

Do you realize that Access tries to write to system tables when a user opens the database? These are hidden tables. Use the Tools / Options to unhide them.

Even if all your tables are linked to an external source, Access will still use the system tables. If a user does not have write access to the database, it will complain.

Also, if you are opening an Access 97 database with Access 2000, and have chosen not to convert it, Access will display the message that changes can not be made.

Richard

 

[jerryreed]

Thanks for the prompt response. I've checked the Hidden Objects option within the Show frame from the Tools/Options menu within the mdb design view. Unfortunately, the user still receives the 'database is read-only' message. I appreciate the thought though.

 

[cghoga]

When you say security properties for the mbd do you mean just on the mdb file?

Make sure the users are given enough control to the DIRECTORY the mdb is located because when you open the database Access will want to create a "YourDBName.idb" file. if the users only have read access to the directory it might give an error because Access is trying to create this .idb file.

just a thought...

 

[willir]

jerryread

Security properties for the mdb as set up as Full Control for Admin (myself)
and Read & Execute and Read for all Users.

Is probably the issue. To write to the system tables, they need full access to the database. Otherwise Access complains.

From my perception, what this boils down to is that Access databases are some what lacking when deployed to the network. The user needs full access. To accomodate the security issue, Access security has to be invoked. The internal Access security is pretty good, but it would be nicer if Access, a Microsoft product, would permit security at the file level and directory as well.

Richard

 

[jerryreed]

Thanks guys -- I'll start testing the security settings for all users to 'Full Control' and go from there. Again, appreciate the responses.