Workgroup file (system.mdw) problem

[jellobze1]

I recently created a workgroup for an access database and it works fine. But I have other versions of that same database (beta copies) for which I didn't create that workgroup file. They have different names than the first DB for which I made the workgroup.
But even when I open those beta copies it still launches the workgroup file (system.mdw) and prompts me to login. What do I need to do to revert these changes and go back to the unsecured version of my database?

Is it as simple as deleting this file?

Thanks in advance,

Angelo

 

[Len Boorman]

Access Security of which the mdw file is a very important part is a minefield for the unwary and I think you have set off a whole bunch of them.

Do not Delete the System.mdw file.

You never use the System.mdw file for any secured database ever. You often copy and rename it.

So Suggested actions

1) delete the secured Access Database
2) Get a copy of System.mdw from a pc where it has not be used for securing a database and overwrite your system.mdw to get you back to square 1

Hmmmm It may work if you simply overwrite your existing System.mdw with a clean copy although I cannot be certain. Maybe somebody else can offer advice on this point.

3) send me a privat message that gives an email address wghere I can send a couple of documents that explain Access Security and why you have the problems you have.


Len Boorman

 

[jellobze1]

Len, thanks for the advice and yes, i do believe i opened a can of worms.
1. i had already deleted the secured database. However, it still prompts me for login and denies access to design changes even when I open a completely unrelated db. I think i might have set off some "join" command under the security/workgroup administrator from the file menu. I recall reading that that redirects all the db's on this pc to that workgroup file on open. i think i might have to undo that but as to how, i am completely clueless.

i really need to undo this fast. Any help is very much appreciated.

Almost desperate,
Angelo

 

[Len Boorman]

Okay

Over write System.mdw with a clean copy from another machine. The reason you are prompted for a login is that System.mdw now has security information.

Documents on way. Replacing System.mdw will get you out of hole but be aware that setting up security the first time will take you 4 hours if you go about it carefully.

You should spend an hour reading the documents and ensuring you understand

Good Luck

L

 

[jellobze1]

ok, will try this.
Angelo

 

[crooshtina]

Hi Len,

Is it possible to post this information? I'd like to take a look as well.

Thanks,

Christina

 

[The_Doc_Man]

First and foremost, everyone asking questions about this topic should search the forum for "WorkGroup" and "Securing" and similar keywords. This topic has been posted no less than a GAZILLION times.

Second, the thing to know about workgroups is that, despite it being something you don't use unless you are using Access, it isn't a database thing. It is a REGISTRY thing. When you JOIN a workgroup, you update your registry setting. If you don't join a new workgroup when you are done, you are STILL in the same workgroup. And you cannot UNJOIN a workgroup. You can only join another group (including the default one which is SYSTEM.MDW). It doesn't matter whether SYSTEM.MDW still exists. (But you can create a new one if it doesn't.)

Here is the thing that escapes lots of folks. In the absence of some very clever operations to avoid the situation, YOU WILL STAY IN THE SAME WORKGROUP ACROSS REBOOTS!!! Once a workgroup has you there is no escape. The reason you need to have a "vanilla" version of SYSTEM.MDW is that it is the workgroup you join when you don't want to be in another workgroup. Because it is the workgroup that has the minimum security settings for everything.