"You do not have necessary permissions to use the .mdb oject"

[Joe]

Hello,

I ran the user-level security wizard on my database and now I cannot
open it. It would prompt me for a password, but i never created one.
I tried leaving the password blank, but that didn't work. I also tried
using the password provided to me on the "one-step security wizard
report", but that also did not work.

So, in my frustration, I deleted the .bak and .mdw files to try and
revert the security, but that just made things worse. I now know that
this was incredibly stupid, but unfortunately the files were on a
network drive, so i can't retrieve them. I am now getting the "You do
not have necessary permissions to use the .mdb oject" message.

This security problem is only happening with this database, and it is
happening with every user that tries to open it.

Is there anyway I can access this database, or do i have to start over?

What are the PIDs used for?

Thanks for your help,

Joe

 

[Joan Wild]

I ran the user-level security wizard on my database and now I cannot
open it. It would prompt me for a password, but i never created one.

I assume it's prompting you for username and password?

I tried leaving the password blank, but that didn't work. I also
tried using the password provided to me on the "one-step security
wizard report", but that also did not work.

Are you entering a correct username? Access will default to the username of
the last person who logged in on your computer (and the first time it will
use the Windows login name). You may have to change that username. I could
be wrong, but I don't think the wizard report gave you the password, just
the PID - they are not the same thing. Also keep in mind that the password
is case sensitive.

So, in my frustration, I deleted the .bak and .mdw files to try and
revert the security, but that just made things worse. I now know that
this was incredibly stupid, but unfortunately the files were on a
network drive, so i can't retrieve them.

Big ouch. The bak file was your unsecured backup of the mdb. Since it's on
a network, it likely (maybe) was being backed up routinely. You could try
and restore from a backup.

I am now getting the "You do
not have necessary permissions to use the .mdb oject" message.

The wizard would have created a desktop shortcut to launch the secure mdb.
Try using that shortcut; provide a valid username and password (try a blank
password).

Is there anyway I can access this database, or do i have to start
over?

If you can't get in, post back with the version you are using.

 

[John Vinson]

I ran the user-level security wizard on my database and now I cannot
open it. It would prompt me for a password, but i never created one.
I tried leaving the password blank, but that didn't work. I also tried
using the password provided to me on the "one-step security wizard
report", but that also did not work.

Download a copy of the Microsoft Access 2000 Security FAQ:

http://support.microsoft.com/kb/207793/en-us

Study it CAREFULLY. As you have vividly demonstrated, it's quite easy
to do security *wrong*, and - unless you have the pre-security
database backed up - it may be difficult indeed to get it back.

The document describes the use of PID's in detail; if (as I hope you
did!!!) you recorded the PID used to create your user accounts, you
can create a new MDW file with the same accounts, and (hopefully)
reset the passwords.

John W. Vinson[MVP]

 

[Joe]

I was able to get back into my database, even though i'm not exactly
sure how it worked.

I created a new workgroup, then ran the user-level security wizard. I
put the same exact PID's in as the original workgroup, then i
referenced the new workgroup file in a shortcut to open the database.
I was then able to access the database. I gave every group and user
admin access. Now, i can open the database without even being prompted
for a password.

I noticed that the workgroup administrator is still referencing my
newly created workgroup file. My question is, will this be a problem
when network users try to access this database? Is there a way to
completely remove the workgroup and security settings from the
database?

Thanks for your help.

 

[aaron.kempf]

Access MDB is

a) insecure
b) a pain in the butt
c) obsolete

if you kept your data in a DATABASE like SQL Server for example; then
you could have real security.

MDB is obsolete; and it has been for almost a decade.

-Aaron

 

[Joan Wild]

I was able to get back into my database, even though i'm not exactly
sure how it worked.

I created a new workgroup, then ran the user-level security wizard. I
put the same exact PID's in as the original workgroup,

That's why it worked. Because you provided the exact same PID, it created
the same workgroup file.

referenced the new workgroup file in a shortcut to open the database.
I was then able to access the database. I gave every group and user
admin access. Now, i can open the database without even being
prompted for a password.

OK, I assume that's what you want?

I noticed that the workgroup administrator is still referencing my
newly created workgroup file. My question is, will this be a problem
when network users try to access this database? Is there a way to
completely remove the workgroup and security settings from the
database?

Yes there is. You don't mention version, so I am assuming either 2002 or
2003 (if you are using an earlier version, *don't* do the following (post
back)).

Use Start, Search and locate all *.mdw files on your computer (be sure to
search in hidden and system folders). Rename every last mdw file you find
e.g. system.mdw - change to system1.mdw
etc.

Now open Access. Create a new mdb file. Import all objects from your mdb.
You are now looking at a completely unsecured copy of your database.
What you've done here is forced the creation of a new system.mdw and created
a database that is owned by the 'Admin' user (as all unsecure mdb files
are). Since you gave full access to all users/groups in your 'secure' mdb,
the Admin user in this new mdw is able to import/gain ownership of all
objects.

If you look in the workgroup administrator, you'll see that it is now using
a newly created pristine workgroup file named system.mdw.

Feel free to delete all other mdw files, and any old copies of your database
(maybe back them up first though - can't be too careful).

 

[aaron.kempf]

you're using 2002/2003 but you're still using MDB?

you know that there is a new format that is superior-- in EVERY
POSSIBLE MANNER.. right?

-Aaron

 

[Joe]

The database is in 2000 format.

Aaron, are you going to provide a suggestion? I don't have access to a
SQL server database at my work.

 

[aaron.kempf]

microsoft.com/sql look for the SP4 download.. choose the MSDE
download..

install it on your desktop; get helpdesk to give you an extra stick of
memory

run the upgrade

buy the $49 developers' edition of SQL 2000.. or just use the free SQL
2005 Express Edition Management Studio to edit objects on SQL 2000
(MSDE 2.0)

Live learn and love TSQL; writing sprocs is a lot more fun than queries

And you dont have splitting; frontend; linked table manager.. just keep
everything in one place.

And read www.sql-server-performance.com

Rinse and repeat

-Aaron

 

[Joan Wild]

Yes, but what version of Access are you using? (Help...About will tell you).
2000, 2002, and 2003 all use the 2000 format by default.