Admin does not have permission to use data base

[Guest]

Everytime I try to open my data base I get back the following message:

"You do not have the necessary permissions to use the "data base name"
object. Have your system administrator or the person who created this object
establish the appropriate permissions for you."

I created the data base and I am signing on as Admin. Could someone have
wiped out the admins permissions? If so, how do I correct this?

Thanks!

 

[Scott McDaniel]

Apparently you implemented Access Security. Did you build a workgroup and
join it? If you did this, and if you used the security wizard, then the
Admin user would no longer have any rights on the database. Normally you
create another user and place that user in the Admins group. Did you do so?
If you did, then log on as that user and setup other user accounts and such
with that login.

You can also try rejoining the default system.mdw workgroup file. To find
out what workgroup you're currently joined to, do this;

Access 2002/2003
==============
Open Access, but don't open any database. Click Tools - Security - Workgroup
Administrator

Access 97/2000
===========
Do a filesearch for "wrkgadm.exe" and run it.

In either case, you'll find out which workgroup file you're joined. To
rejoin the system.mdw file:

Do a filesearch for "system.mdw". Using one of the methods above, run the
Workgroup Administrator, and click "Join" and join the system.mdw file found
earlier.

Generally speaking, it's a good idea to setup a desktop shortcut to log onto
your secured database. To do that, create a new shortcut and set this as the
Target:

"FUll path to MSAccess.EXE" "Full path to your db" /wrkgrp "Full path to
your workgroup file"

Here's a link to the MS whitepaper regarding Access security:
http://support.microsoft.com/Defaul...crosoft.com/support/access/content/secfaq.asp

 

[Guest]

Scott:

Thanks for the reply. I was working on a different PC on the network trying
to build a short cut on the desktop back to the data base PC. I copied over
the workgroup and joined it. And yes I used the Access Security, (which may
or may not have been right). Problem is I can't access the data base on the
original PC will I am sitting at it. In fact the error message comes up just
trying to open from the shortcut. You don't even get a chance to enter an
User and password. I am working with Access 2000 BUT the data base was
originally built in Access 97. I tried removing all the workgroup files
which open up all the back-up copies but I still can't gain access to the
current version of the data base.

I tried copying the data base and loading it on another stand only computer
but still get the same error message. If Admin can't open the file and I am
given no chance to enter a User Id and password how do I get around this
"lock" and retreive my data?

 

[Scott McDaniel]

It sounds as if you're joined to the wrong workgroup file, or that the Admin
user no longer belongs to the Admins group. Do you remember the name of the
workgroup file you created when you implemented security? Try to locate that
file and join it on the machine where you're having trouble. Again, the
Admin user was most likely removed from the Admins group, which means it has
no permissions. You'll have to log in using another Admins member ... if you
used the Security wizard, then you were probably prompted to add a user to
the Admins group.

Did you try joining system.mdw? Sounds like it may not work but you can try
this.

 

[Guest]

It appears as if Access changed all the permissions on all the data base
objects to "off" even for the Admin. From what I see in the White papers
this should not be possible.

 

[Scott McDaniel]

The security wizard will (a) remove the Admin user from the Admins group
(thereby removing all permissions from the Admin user) and (b) remove all
permissions from the Users group, so this would be expected behaviour. If
you didn't add any additional users, and especially if you didn't add a user
to the Admins group, you may be out of luck

Again, what workgroup are you joined to? Have you tried rejoining the
system.mdw file?

 

[Joan Wild]

In
fact the error message comes up just trying to open from the
shortcut. You don't even get a chance to enter an User and password.

What is in the target of this shortcut?

 

[Guest]

How nice of the security wizard. So it appears that the security wizard
changed the actual data base and didn't just play with the workgroup files on
the new PC. In other words, it accessed the data base on the original PC
across the network and wiped out the admin account. But it sounds like if
another user had admin rights they could still get in to the data base. I
will try this.

I have tried joining both the pre-existing workgroup and the system one.
Neither work. I even tried creating a new one. I think you might be right
about being out of luck. I tend to believe that the security wizard changed
the ownership and the read, write, update permissions to off period.

I will post back after I have another user with admin rights logon. If this
doesn't work I think I am sunk.

 

[Scott McDaniel]

Yes, the security wizard changes permissions on objects in the database (it
tells you it's doing this, BTW). It also (normally) creates a new database
and moves all objects to that database so that it can change ownership of
the objects to whatever user you indicate. The Admin account (and all other
User and Group info) is stored in the workgroup file, NOT the database. The
security wizard would remove the Admin user from the Admins group in
whatever workgroup your "told" it to use (including one you told it to
create, if you did so). So if you ran the security wizard and told it to use
a workgroup file on your "other" PC across the network, it would do so. It
would NOT, however, remove permissions from another database ... only the
one from which you ran it.

By read/write/update, do you mean Access permissions or Windows permissions?
The security wizard does nothing in regards to Windows permissions.

Here's Lynn Trapp's 10 step process to secure a db. It tells you what's
going on in regards to security, and basically does the same thing the
security wizard does. perhaps it'll help you understand exactly what
happens: http://www.ltcomputerdesigns.com/The10Steps.htm

 

[Guest]

Joan, per Scott's original message:

"Generally speaking, it's a good idea to setup a desktop shortcut to log onto
your secured database. To do that, create a new shortcut and set this as the
Target:

"FUll path to MSAccess.EXE" "Full path to your db" /wrkgrp "Full path to
your workgroup file""

....that is the shortcut.


Max...

 

[Joan Wild]

Hi Max,

You've confused me. The original post is from 'kevin'. Who is Scott?

(and this thread is over a month old; are we still talking about the same
problem?