Db suddenly becomes Read Only 1

[LarryDeLaruelle]

Using Access 2000; SP3. Windows XP Pro OS.

Application has been up and running for several weeks with no problem. Front end is downloaded to the user's system; back end resides on a server.

User attempted to do data entry today and received an error when writing a new record that the database was read only.

I opened the back end db on the server and received a message that the db is read only; when any table is open in datasheet view, there is no blank line available. I can open a table in design but not create any new object (table, query, form, etc).

I checked the db file properties and it is not checked as read only. No other file in that folder has been affected. I checked the db's internal properties and read only is not checked although it is grayed out.

I created a new, blank database and linked the tables from the back end and was mostly successful. Some linked tables did not display all the records that would be shown when viewing from the back end (in fact, the main table was completely empty).

I solved the problem by doing a series of make tables queries from the original front end and saving the new tables into the new back end.

This gets me back in business but I'm concerned about what caused this db to suddenly become read only. Would anyone have experienced this or have any idea of how/why it happened?



Larry De Laruelle

 

[Remou]

Did you check the permissions of the folder?

 

[LarryDeLaruelle]

Remou, thanks for responding.

Yes I did. Folder is fine as well as all other files in that folder. The only file that has been affected is the original back end db.

Larry De Laruelle

 

[Remou]

What about the .ldb? Did an .ldb remain after the back-end was closed?

 

[LarryDeLaruelle]

This has gone beyond weird. The database is now fine.

I just opened it again and no messages. I can create new object. I can add records.

I've got about 10 to 5:00PM; I'm calling it a day and going home.

Thanks for the help Remou. Don't know what you did or didn't do, but I'll give you and assist on this one.

Larry De Laruelle

 

[lameid]

By chance do some users have read only access to the folder and others have change permissions?

I've found Access will allow a ton of read only people in without an LDB file (locking file) but won't let them in if an LDB file exists. Conversely, if the LDB file exists and the Access won't let the Read only user in because he can't write to the LDB file.

If this is not even it, you might check to see if there are problems with access and the security products being run in the network, both file server and clients.

 

[LarryDeLaruelle]

lameid:

You may be on to something. Common users have Read & Execute, List Folder Contents and Read permissions. Data Entry staff also have Modify and Write permissions.

I do remember that I did not see an .ldb file in the folder when I first started checking this. Is it possible that a read-only user had the db open and somehow it was open exclusive? Would that cause the behavior I saw?

Thanks.

Larry De Laruelle

 

[lameid]

Ultimately it is locking but it is more involved using the LDB file, as I described.

You could give all users with permissions change permission to the folder (write) but there is a major caveat. When you compact and repair a database, it technically creates a new file and when it is done deletes the original. The new file inherits the permission of the directory, killing any restrictive file permissions you may have set.

 

[LarryDeLaruelle]

Lamied:

Thanks. I've talked to our IT folks and we will give common users the permissions needed to create the ldb file. The compact repair should not be a problem, I do those during off hours.

Thanks again.

Larry De Laruelle

 

[lameid]

Who is going to fix the permissions when you create the file in off hours?

A work around is to compact and repair to sub folder with correct file permissions and then move it to the production folder.

Actually, the location of the "sub" folder does not matter as long as it is on the same Server.

 

[LarryDeLaruelle]

Lameid:

We've used this process successfully in the past for other databases. I think yesterday's issue was principally that the common users did not have necessary permissions on the folder where the back end lives. That's been addressed for this problem by giving them write and modify permissions.

Thanks again.

Larry De Laruelle

 

[lameid]

I'm sorry, I thought you would have been concerned about giving them more permission than they already had.

I only mention it then for anyone who may find this thread later and is concerned about the permission issue.

 

[LarryDeLaruelle]

Lameid:

I understand and should have considered that myself.

This has been an invaluable site for me over the years. A place to go for expert assistance.

Thanks Again.

Larry De Laruelle