Database is read only?

[Gkirkup]

I routinely export queries etc from my development database to the 'live' master database used by users. Every so often I get the error message 'The database Mydatabase.accdb is read only'. Then I can't export anything to it. I don't know why it should suddenly become read only. How do I make the database changeable, and not read only?

Robert

 

[Pat Hartman]

Objects in a database should NEVER be modified while the application is opened by another user. All object changes to your master database should be done with the users logged out. Besides, the users shouldn't be using the same physical copy of the FE anyway. Each user should have his own personal copy, loaded on his own c: drive. Only the shared BE stays on the server.

 

[Gkirkup]

Pat: Sure! That is exactly what we have. We have one copy of the back end on a server, and multiple users with front ends on their computers. But we also have a 'master' front end on the server. No one runs that, but everyone gets a copy of it automatically when there are program changes to the master front end.
My question was, sometimes when I export new forms or queries etc to the master front end, it refuses to do it, saying that it's read only. Could that be because the master front end is being copied to a user? (This happens when a user restarts, and is based on version numbers on the front end).

Robert

 

[MSAccessRookie]

Pat: Sure! That is exactly what we have. We have one copy of the back end on a server, and multiple users with front ends on their computers. But we also have a 'master' front end on the server. No one runs that, but everyone gets a copy of it automatically when there are program changes to the master front end.
My question was, sometimes when I export new forms or queries etc to the master front end, it refuses to do it, saying that it's read only. Could that be because the master front end is being copied to a user? (This happens when a user restarts, and is based on version numbers on the front end).

Robert

Just to verify your process:

• Testing should not be done using a Master Version of the Database.
• The Database should be copied to a work area (FE and BE adjusting Links are required). It can then be modified in whatever manner is required, and tested before it is restored.
• Once the Modified Version of the Database is tested and approved, the Master Copy can be archived and the Modified Version can be moved in to replace the Master Copy. Updating should be done as a whole Database and not one piece at a time, because in the event that someone logs into the database during the update, they might only get a partial update.

Using these practices could limit your exposure to failure during updates.

-- Rookie