Error 3027 - Read-Only Access to access (1 Viewer)

[DJanton]

Hi,

A major problem here ever since the manager had to restore Novell network software and re-setup the users.

Now Access file pops up a message Database or object is read-only (3027). The Access file itself does not show read-only attribute on. The folder where the file resides has all the access it can get for every action. Please keep in mind, nothing has changed under user and group security, and access was not re-installed.

Can anyone make a good guess as to where to look next?

Thank You.

 

[Travis]

Have you check to see if the corresponding LDB file is getting created when you try to access the MDB file?

If the LDB file is in the directory is it set to "Read-Only"?

If you copy the Access file to a local PC can you Open it without the Read Only Error?

 

[DJanton]

Error 3027 - Read-Only Access

Yes, after copying to a local pc I can open the access DB no problem.

Thank You.

 

[TessB]

Thread revived for follow-up!

Pat,
Just read this thread and it was extremely helpful to us here. This morning, when one of the users tried to open a shared database on the network drive, they were not able to add or modify anything. They were using Runtime so they did not receive the "This database is Read-Only" message that I got when I opened the database myself to try and trouble-shoot the problem. The database was not marked "Read-Only" in the properties, but for some reason, it was in a Read-Only status until just now when most users have shut down and gone home for the evening. After reading this post, I am thinking that maybe some users do not have create and delete rights.

Usually, we get another error like "File is already in use" and we have to wait until whoever locked the database to shut down his/her PC and go home before we can access it again.

We would like to solve this problem once and for all.

BUT, we also have experience an even greater problem which we would like to solve. The other day, someone actually deleted our database and we had to get it restore from tape backup. (Managers were NOT happy losing a day of use!) We thought, maybe we should put it on a drive where we are the only ones who can delete the files? But that would definitely perpetuate the initial problem of users hanging up the database!

What would your suggestions be for addressing these issues?

Respectfully, with thanks,
Tess

 

[The_Doc_Man]

We have a database shared through Novell services.

Here is the problem.

In order to repair or compress a database you need to be able to create and delete the .MDB file. Any other time, you can remove the delete permission. So you take away everyone else's right to delete the .MDB file. That still leaves YOU with the problem that you need to delete the file when doing maintenance.

So what you do is you get your boss to talk to the sys admin on the shared box. Then you schedule a time during which you get to exercise your Open Exclusive privelege. Call your sys admin. Get him/her to grant you DELETE rights on the .MDB. Do your maintenance. Then you call the sys admin and say, OK, remove the DELETE rights off the new .MDB file.

The key is that the sys admin's boss needs to be in the loop to, shall we say, explain gently but forcefully that this tedious little procedure is required for company operation. Then add the little caveat, "unless you want to give someone else the rights to administer that particular directory..."

The sys admin won't like it but will immediately agree to the other pain in the toches (regular manipulation of rights) in order to avoid having to lose control. Or, you'll be lucky and the sys admin will agree that you can administer the folder.

In any case, NO ONE needs rights to delete the DB except you, so what you do is, for that one file, assure that it does NOT inherit its protection codes from the parent directory. (It's a check box in the security screen for Netware.)

 

[TessB]

Database gets switched to read-only


I need a crying smilie!

Issue:
Built a database which one user with Full Version Access has been using successfully for a week or so. RunTime Access was installed on other users PCs and a shortcut to the database placed on their desktops.

The database is on the network, not an SQL server. On Friday, I found the database had turned into a Read-Only database. I knew from this and other posts that this can happen if the users do not have Write and Delete rights to the drive.


I couldn't delete the database, or rename it, so it's still out there. I made a copy and went around to everyone (about 12 users) and gave them a new shortcut.

I tested everyone's PC to make sure that when the database was accessed, the .ldb file was created and deleted when the database was exited.

The user with full version of Access worked with the database until lunchtime and then exited when she went to lunch. When she came back, the new copy of the database had reverted to Read-Only. I am at a loss! The database will be a vital part of their job procedures. Where else should I begin to troubleshoot? How can I make sure this will not happen again?

Thanks for your time
Tess