User level security applied to al db's

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I created a database with user level security. The database is called db1.
The problem is that other databases that I have created such as db2, db3 and
so, now behave as if I set them up with user level security which I did not.
the databases that were not set up to have user level security are in
different folders from the one with security implemented.

What this means is that when I now try to create a new database or open one
of the non-secure databases the Logon dialog box is displayed asking for Name
and Password.

What is causing this?
 
You have "joined" your computer to a secured workgroup file that is
asking for the login ID and password. You need to "join" the default
workgroup file that is unsecured. It is usually called system.mdw, and
you join it by using the workgroup administrator process. Exact method
varies depending on the version of Access you are using. In latter
versions of Access, you run it from the Tools > Security menu.

Once you have rejoined your computer to the default workgroup file,
then your databases will open without requiring a loginID and
password. In order to use security for the *single* database, you must
temporarily join the secure workgroup by encoding the information into
a desktop shortcut for the database. This is the syntax to use in the
shortcut's target:

<fullPathToAccess.EXE> <fullPathToYourDatabase.MDB> /wrkgrp
<fullPathToWorkgroupFile.MDW>

Replace the filenames with the appropriate names on your computer.

See the website in my signature for links to documents that will
explain in additional detail.

I created a database with user level security. The database is called db1.
The problem is that other databases that I have created such as db2, db3 and
so, now behave as if I set them up with user level security which I did not.
the databases that were not set up to have user level security are in
different folders from the one with security implemented.

What this means is that when I now try to create a new database or open one
of the non-secure databases the Logon dialog box is displayed asking for Name
and Password.

What is causing this?
Click to expand...


**********************
(e-mail address removed)
remove uppercase letters for true email
http://www.geocities.com/jacksonmacd/ for info on MS Access security
 
Thanks Jack,
that is a great help as I could not find any information regarding this in
my Help files. Does this mean that every time I create a secured database
that I will have to use the method you have described or is there a method I
can use which will automatically only associate a workgroup file with the
database it was created in.
Cheers.
 
If you have not specifically created a workgroup file associated with this
database, you might have inadvertently set user level security into
system.mdw, which is causing this error.
 
AdeyS wrote:

(snip)
Does this mean that every time I create a secured database
that I will have to use the method you have described or is there a method I
can use which will automatically only associate a workgroup file with the
database it was created in.
Click to expand...


There is no such public method at present.

HTH,
TC
 
Mr. MacDonald,

I want to tell you that your posts have been extremely useful to me (as well
as your website). I have followed the posting and advice to walk through
database creation from start to finish. God bless you for the answer below.
This was the last piece in getting my database operational and I simply did
not know how to write in the proper syntax to open the db with the associates
..mdw

The judges say "10" "10" "9.8" "10" "9.6" "10"

Well done Jack, and thank you

Nathan (Bar-Tolemai) Clary
 
Back
Top