Usurped Creator of Database

[Wayne]

I created a database on a network drive of the company I work for. My MS
Access 2000 SP3 is on my C drive. I successfully created User-level security
using the Security Wizard. I was created an ID for myself and successfully
used my ID with Admin, Full Permissions, and Full Data User groups. However,
people not using my computer were not able to use the IDs and passwords that
I created for them. To allow others to view/open/run some elements of the
database, I granted the users some permissions. Other users were able to get
into the database and use the permissions available to all users without
logging in.

Somehow in the process of granting permissions for general users, I lost the
ability to log in myself from the computer I created the database with. I
know the log on ID and the password, but I can't seem to get the system to
prompt me for the ID/password.

I viewed some of the other discussions on security. I tried to rejoin the
system.mdw and created a shortcut for the database per the instructions in
another post (Then use a desktop shortcut to launch your secure mdb The
target would be "path to msaccess.exe" "path to mdb" /wrkgrp "path to secure
mdw").

Nothing has helped. It does not seem to matter if I am joined to the
secured.mdw of the database with security or system.mdw.

Please help.

 

[Joan Wild]

I created a database on a network drive of the company I work for. My MS
Access 2000 SP3 is on my C drive. I successfully created User-level
security
using the Security Wizard.

If you used the Wizard in 2000, then you did not successfully secure it,
sorry; the wizard is flawed in 2000.

You need to secure it manually. Follow the detailed step-by-step at
http://www.jmwild.com/security97.htm

I was created an ID for myself and successfully
used my ID with Admin, Full Permissions, and Full Data User groups.
However,
people not using my computer were not able to use the IDs and passwords
that
I created for them.

Are you certain you are using the correct passwords - the PID is not the
same as a password; usually a password is blank/null initially.

To allow others to view/open/run some elements of the
database, I granted the users some permissions. Other users were able to
get
into the database and use the permissions available to all users without
logging in.

The flaw in the 2000 wizard. You need to start over with an unsecured copy
of your mdb.

Somehow in the process of granting permissions for general users, I lost
the
ability to log in myself from the computer I created the database with. I
know the log on ID and the password, but I can't seem to get the system to
prompt me for the ID/password.

The 'Admin' user in the secure mdw (not system.mdw) needs to have a password
set - that's what causes the login dialog to appear.

I viewed some of the other discussions on security. I tried to rejoin the
system.mdw and created a shortcut for the database per the instructions in
another post (Then use a desktop shortcut to launch your secure mdb The
target would be "path to msaccess.exe" "path to mdb" /wrkgrp "path to
secure
mdw").

Nothing has helped. It does not seem to matter if I am joined to the
secured.mdw of the database with security or system.mdw.

That indicates that it wasn't secured properly.

 

[Wayne]

If you used the Wizard in 2000, then you did not successfully secure it,

sorry; the wizard is flawed in 2000.

The security appeared to work well until I used the wizard to increase the
regular user permissions.

Are you certain you are using the correct passwords - the PID is not the
same as a password; usually a password is blank/null initially.

I was using the correct passwords. Again, logging in from my computer worked
fine until I added permissions to the regular users (people without a special
ID and password).

The 'Admin' user in the secure mdw (not system.mdw) needs to have a password
set - that's what causes the login dialog to appear.

That is good to know. How do I get the 'Admin' user to have a password? the
secured.mdw only has queries. I do not see any tables. Are the tables hidden
files, or do I need to enter the password directly into the queries?

Thanks again,
Wayne

 

[Joan Wild]

The security appeared to work well until I used the wizard to increase the
regular user permissions.

I never use the wizard, but my understanding is that you shouldn't let the
2000 wizard touch your database.

I was using the correct passwords. Again, logging in from my computer
worked
fine until I added permissions to the regular users (people without a
special
ID and password).

Are you adding permissions to groups (recommended) or to users? You can add
permissions to users, but it is harder to manage them.

That is good to know. How do I get the 'Admin' user to have a password?
the
secured.mdw only has queries. I do not see any tables. Are the tables
hidden
files, or do I need to enter the password directly into the queries?

Use your shortcut to start the database (assuming you have a shortcut that
specifies the /wrkgrp switch followed by a path to your secure mdw).
Dismiss the message about having no permissions, and then go to Tools,
Security, Accounts, Change Password tab and change the password from null to
something.

 

[Wayne]

Joan, thanks for your help.

Using the step on the weblink from your first reply, I created a new
database with the correct security (avoiding the wizard like the plague).
Since, I was never able to a login for the old database, I deleted the old
MDW file, which made the owner of the old database unknown. I was able to
then import all the old data into the new database and everything works like
a charm!!!