"Read-Only ?" What have I done? 2

[rod1968]

I have a number of databases on a development machine and I made a change to in the advanced options from "exclusive" to "shared" option. Since I did that, I cannot get into any of my databases without getting the message "Can't Update - Database or Object is Read Only"

What have I done and how can I regain access ?

Can anyone help me please ?

 

[rod1968]

I now think I have done something to my "system.mda" file as it seems to be missing from my Access directory

Has anyone had experience of this and what do I do if I don't have a backup ?

 

[Kubilus1]

What OS are you running. In NT right click on the database file go to properties/security/permissions. Try setting full-control for everyone. Good luck.

Matt

 

[rod1968]

Well it appears that I had somehow removed myself as administrator from all the databases I wrote and administer. I bit of a problem eh ?

The good news is that, as if by magic, I seemed to have become administrator again ... not sure what had happened but every thing seems OK again.

Incidentally, I was using OS Windows 95 and Access 95 ... soon I need to upgrade all the databases to Access 2000 ... I hope that goes without similar incident Many thanks for your reply Matt, I appreciate it.

 

[RickSpr]

Since your administrator rights on all the databases disappeared and reappeared simultaneously, it's most likely that you switched workgroups using the Workgroup Administrator. Having the same name in different system databases isn't enough; permissions depend on both the user name and the PIN.

If you want to be able to use different workgroups to administer a database, you must create the user account with identical details in each workgroup. Since you already have a user account with the wrong PIN in at least one workgroup, you might have a problem changing it at this point. If you've already assigned permissions based on this account (with the wrong PIN), deleting the account and adding it back with the proper PIN will lose those permissions. (The permissions will still be stored in the database, actually, but you won't be able to get to them when you log on with the corrected PIN.)

The best procedure is to log on with another administrator account, go into each database in which the erroneous account has permissions, and remove all the permissions. Then delete and recreate your user account, and go back into each database and recreate the permissions for the new account.

Hope you can follow this. Without having any database or account names to mention, it's hard to distinguish which one I'm talking about for you.
Rick Sprague