G
GYoung1
Hello,
I am posting this message in hope someone can help me. Any help is
most appreciated.
I have an Access 2002 database that was secured using the User Level
Security Wizard (Tools | Security | User Level Security Wizard). In
other words, the wizard secured the database and created a new
workgroup information file and a desktop shortcut to the database.
This was all done on my computer. The original database name was
Main.mdb. Before I secured the database, I copied the original
database mdb file to be secured and named it MainSecured.mdb. So,
before running the security wizard, I had 2 mdb files the original
unsecured mdb (Main.mdb) and the secured mdb (MainSecured.mdb) files.
(Actually the wizard also created a backup of the database with the
extension .bak so there are actually 3 copies.)
To repeat, I have the original unsecured database called Main.mdb.
I have a secured database called MainSecured.mdb.
These files are located on my computer in the folder D:\CPC where D is
the D Drive and in the folder called CPC.
On a side note, I am actually using Access 2003 if that matters. The
database window lists the database mdb file as Access 2002 - 2003 file
format.
Here is some additional background. I am working on this database for
a client. My client has an exact copy of the unsecured database also
called Main.mdb but it is stored on their network with the path
(mapped drive) such as "S:\Sacramento\Database". As you can see our
copies of the database are stored in different folders and drives.
However, the databases are exactly the same and have the same name.
Now onto my problem. I normally like to make changes and corrections
to my copy of my database on my local computer. Then, I like to import
any changed objects such as new queries or new reports. That works
terrific on the unsecured database.
Using the same logic, I have created the workgroup information file
called security.mdw and copied that file to the client's computer. I
then copied my secured database called MainSecured.mdb to the clients
computer and put it into the folder "S:\Sacramento\Database".
I next setup the desktop shortcut to the database. On my computer,
the shortcut TARGET Line is:
"D:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" "D:\CPC
\MainSecured.mdb" /WRKGRP "D:\CPC\Security.mdw”
I recreated this desktop shortcut on my client's computer by modifying
the target line to point to the correct folder "S:\Sacramento
\Database". In other words, in the target line after MSACCESS.EXE”,
it reads "S:\Sacramento\Database\MainSecured.mdb" /WRKGRP “S:
\Sacramento\Database \Security.mdw”.
As you can see, the client’s shortcut target line and my shortcut
target line are similar only that they point to different folders.
I wanted to demonstrate the secured database to my client after
copying the files to my client’s computer.
I was expecting the database to work exactly like it did on my
computer. The only difference is that the folder where the workgroup
information file named security.mdw and MainSecured.mdb file are
placed. On my computer, these files are both in the folder D:\CPC and
on the client's computer these files are in the folder "S:\Sacramento
\Database".
Again, I copied both the workgroup information file named security.mdw
and the MainSecured.mdb file into this folder on the client's
computer.
At this point, if I double click the shortcut icon, the database
should open and prompt for a username and password. When I did this,
the database opened without any prompt for a password. It acted like
it was unsecured. Why is this happening? For some reason, the
default user Admin is logging in without any password. By the way,
the security wizard removed the Admin user account from the Admins
group and set a password as expected and I also removed all
permissions from the Users group. (In the wizard, you have the option
to assign no permissions to the default built in Users group which I
liked to do for other reasons.) Lastly, I did not change the default
system.mdw workgroup information file currently in use on the client's
computer. The client uses Access for other databases and I didn’t want
to change the default workgroup information file. That was the reason
for adding the desktop shortcut.
What I like to do is secure my copy of the database which I did and
then just copy the workgroup information file named security.mdw to
the client's computer. I was hoping when I did this that the client's
database would then become secured. When I view the user accounts and
groups, they are there so I know by copying the workgroup information
file to the client's computer that it was the same as on my local
computer.
Maybe my workgroup information file is pointing to "D:\CPC" but the
client's computer is pointing to "S:\Sacramento\Database". Is this
hard coded path stored in the workgroup information file? If so, how
can it be updated to point to the folder "S:\Sacramento\Database" on
my client's computer? On my computer, no change is necessary as it is
working properly.
Anyway, if you can help me, that would be great. If worse comes to
worse, I will just have to recreate the workgroup information file
using the security wizard on the client's computer, add the users, add
the groups, and reset all permissions. However, I am hoping I won't
have to redo this. Thanks in advance.
I am posting this message in hope someone can help me. Any help is
most appreciated.
I have an Access 2002 database that was secured using the User Level
Security Wizard (Tools | Security | User Level Security Wizard). In
other words, the wizard secured the database and created a new
workgroup information file and a desktop shortcut to the database.
This was all done on my computer. The original database name was
Main.mdb. Before I secured the database, I copied the original
database mdb file to be secured and named it MainSecured.mdb. So,
before running the security wizard, I had 2 mdb files the original
unsecured mdb (Main.mdb) and the secured mdb (MainSecured.mdb) files.
(Actually the wizard also created a backup of the database with the
extension .bak so there are actually 3 copies.)
To repeat, I have the original unsecured database called Main.mdb.
I have a secured database called MainSecured.mdb.
These files are located on my computer in the folder D:\CPC where D is
the D Drive and in the folder called CPC.
On a side note, I am actually using Access 2003 if that matters. The
database window lists the database mdb file as Access 2002 - 2003 file
format.
Here is some additional background. I am working on this database for
a client. My client has an exact copy of the unsecured database also
called Main.mdb but it is stored on their network with the path
(mapped drive) such as "S:\Sacramento\Database". As you can see our
copies of the database are stored in different folders and drives.
However, the databases are exactly the same and have the same name.
Now onto my problem. I normally like to make changes and corrections
to my copy of my database on my local computer. Then, I like to import
any changed objects such as new queries or new reports. That works
terrific on the unsecured database.
Using the same logic, I have created the workgroup information file
called security.mdw and copied that file to the client's computer. I
then copied my secured database called MainSecured.mdb to the clients
computer and put it into the folder "S:\Sacramento\Database".
I next setup the desktop shortcut to the database. On my computer,
the shortcut TARGET Line is:
"D:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" "D:\CPC
\MainSecured.mdb" /WRKGRP "D:\CPC\Security.mdw”
I recreated this desktop shortcut on my client's computer by modifying
the target line to point to the correct folder "S:\Sacramento
\Database". In other words, in the target line after MSACCESS.EXE”,
it reads "S:\Sacramento\Database\MainSecured.mdb" /WRKGRP “S:
\Sacramento\Database \Security.mdw”.
As you can see, the client’s shortcut target line and my shortcut
target line are similar only that they point to different folders.
I wanted to demonstrate the secured database to my client after
copying the files to my client’s computer.
I was expecting the database to work exactly like it did on my
computer. The only difference is that the folder where the workgroup
information file named security.mdw and MainSecured.mdb file are
placed. On my computer, these files are both in the folder D:\CPC and
on the client's computer these files are in the folder "S:\Sacramento
\Database".
Again, I copied both the workgroup information file named security.mdw
and the MainSecured.mdb file into this folder on the client's
computer.
At this point, if I double click the shortcut icon, the database
should open and prompt for a username and password. When I did this,
the database opened without any prompt for a password. It acted like
it was unsecured. Why is this happening? For some reason, the
default user Admin is logging in without any password. By the way,
the security wizard removed the Admin user account from the Admins
group and set a password as expected and I also removed all
permissions from the Users group. (In the wizard, you have the option
to assign no permissions to the default built in Users group which I
liked to do for other reasons.) Lastly, I did not change the default
system.mdw workgroup information file currently in use on the client's
computer. The client uses Access for other databases and I didn’t want
to change the default workgroup information file. That was the reason
for adding the desktop shortcut.
What I like to do is secure my copy of the database which I did and
then just copy the workgroup information file named security.mdw to
the client's computer. I was hoping when I did this that the client's
database would then become secured. When I view the user accounts and
groups, they are there so I know by copying the workgroup information
file to the client's computer that it was the same as on my local
computer.
Maybe my workgroup information file is pointing to "D:\CPC" but the
client's computer is pointing to "S:\Sacramento\Database". Is this
hard coded path stored in the workgroup information file? If so, how
can it be updated to point to the folder "S:\Sacramento\Database" on
my client's computer? On my computer, no change is necessary as it is
working properly.
Anyway, if you can help me, that would be great. If worse comes to
worse, I will just have to recreate the workgroup information file
using the security wizard on the client's computer, add the users, add
the groups, and reset all permissions. However, I am hoping I won't
have to redo this. Thanks in advance.