By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,836 Members | 2,023 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,836 IT Pros & Developers. It's quick & easy.

Secured Access 2000 database: Admin has no rights?

P: n/a
I was given a database to update and am running into the following
problem:

The database appears to have been secured using Access security (it is
an MDB, not MDE). Every form etc that I try to open (in the
development environment) gives me 2 messages:

1) "You do not have exclusive access to the database at this time
etc."
2) "You don't have permission to read frmWhatever... etc."

I suspect the issue might be compounded by the fact that the database
contains many tables that are linked to a SQL Server database that I
do not (yet) have running in my environment.

When I open the database (not in design mode) and the startup form
appears... it appears to have me logged on as Admin (without prompting
me further... this information appears on the startup form).

When I look at Security settings in design mode - it lists my Current
User name as Admin. According to User and Group Accounts information,
Admin is part of the Admins and Users groups.

I cannot, however, do anything in the database and the person who
originally created the database is long gone and the database users do
not have any helpful information (they were not even aware a SQL
Server database is being accessed).

Any ideas how to unsecure the database or to figure out why Admin is
not able to act as one - would be appreciated!

Aliza
Jul 23 '08 #1
Share this Question
Share on Google+
8 Replies


P: n/a
"aklein" <ab*****@optonline.netwrote in message
news:07**********************************@k13g2000 hse.googlegroups.com...
>
Any ideas how to unsecure the database or to figure out why Admin is
not able to act as one - would be appreciated!
I suspect that Admin is not the *owner* of the objects. Try importing the
objects into a new file.

Regards,
Keith.
www.keithwilby.com

Jul 23 '08 #2

P: n/a
Any ideas how tounsecurethedatabaseor to figure out why Admin is
not able to act as one - would be appreciated!

I suspect that Admin is not the *owner* of the objects. *Try importing the
objects into a new file.

Regards,
Keith.www.keithwilby.com
When I try to import a form to a new file - I get the same message: I
do not have the permissions necessary to import the file.

Help?
Aliza
Jul 23 '08 #3

P: n/a
"aklein" <ab*****@optonline.netwrote in message
news:15**********************************@e39g2000 hsf.googlegroups.com...

You need to log in to the database as it's owner which sounds as if it's the
person who applied security. If that's not an option then you may have to
use a third party program to break the security. Perhaps someone else could
jump in here (Joan?).

Jul 23 '08 #4

P: n/a
On Jul 23, 11:08*am, "Keith Wilby" <h...@there.comwrote:
"aklein" <abkl...@optonline.netwrote in message

news:15**********************************@e39g2000 hsf.googlegroups.com...

You need to log in to the database as it's owner which sounds as if it's the
person who applied security. *If that's not an option then you may haveto
use a third party program to break the security. *Perhaps someone else could
jump in here (Joan?).
If anyone can recommend a third party - I would certainly consider
that route.

The original database creator (who I presume set the security) is long
gone... the database objects are listed as an "<unknown>" owner.

I have tried looking at the mdw files (I have found a couple different
options that were sent to me along with the mdb file) but have had no
success.

Any ideas?

(It also is preventing me from updating my linked tables to my local
copy of the SQL Server database.)

Aliza
Jul 23 '08 #5

P: n/a
The db objects show <unknownas the owner because you aren't joined to the
workgroup used to secure the db. People usually make mistakes when trying to
secure a db. One of them is to forget to remove all permissions to the
default admin user. That's why you're able to open the db, even without the
secured mdw file.

Try changing all of the db objects from the <unknownowner to the admin user.
Any objects you can change the ownership of to admin you can import into a
new db where admin is the owner.

Chris
Microsoft MVP
aklein wrote:
>You need to log in to the database as it's owner which sounds as if it's the
person who applied security. *If that's not an option then you may have to
use a third party program to break the security. *Perhaps someone else could
jump in here (Joan?).

If anyone can recommend a third party - I would certainly consider
that route.

The original database creator (who I presume set the security) is long
gone... the database objects are listed as an "<unknown>" owner.

I have tried looking at the mdw files (I have found a couple different
options that were sent to me along with the mdb file) but have had no
success.

Any ideas?

(It also is preventing me from updating my linked tables to my local
copy of the SQL Server database.)

Aliza
--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200807/1

Jul 24 '08 #6

P: n/a
On Jul 23, 11:49*pm, "Chris O'C via AccessMonster.com" <u29189@uwe>
wrote:
The db objects show <unknownas the owner because you aren't joined to the
workgroup used to secure the db. *People usually make mistakes when trying to
secure a db. *One of them is to forget to remove all permissions to the
defaultadminuser. *That's why you're able to open the db, even without the
secured mdw file.

Try changing all of the db objects from the <unknownowner to theadminuser.
Any objects you can change the ownership of toadminyou can import into a
new db whereadminis the owner.

Chris
Microsoft MVP

akleinwrote:
You need to log in to the database as it's owner which sounds as if it's the
person who applied security. *If that's not an option then you may have to
use a third party program to break the security. *Perhaps someone else could
jump in here (Joan?).
If anyone can recommend a third party - I would certainly consider
that route.
The original database creator (who I presume set the security) is long
gone... the database objects are listed as an "<unknown>" owner.
I have tried looking at the mdw files (I have found a couple different
options that were sent to me along with the mdb file) but have had no
success.
Any ideas?
(It also is preventing me from updating my linked tables to my local
copy of the SQL Server database.)
Aliza

--
Message posted via AccessMonster.comhttp://www.accessmonster.com/Uwe/Forums.aspx/databases-ms-access/2008...- Hide quoted text -

- Show quoted text -
Thanks for the idea... but I have already tried to change ownership
and have been told I have no rights. I have also tried to import the
forms and again, was told that I don't have permission to do that.

Hmmmm.... any other thoughts? I appreciate them all!
Aliza
Jul 24 '08 #7

P: n/a
"aklein" <ab*****@optonline.netwrote in message
news:da**********************************@z72g2000 hsb.googlegroups.com...
Hmmmm.... any other thoughts? I appreciate them all!
Google for "ms access password recovery" then take your pick.

Keith.
www.keithwilby.com

Jul 25 '08 #8

P: n/a
What about the other mdw files? Were you given a member of the admins
group's user name and password for each of them so you could try opening the
db with permissions?

Chris
Microsoft MVP
aklein wrote:
>Thanks for the idea... but I have already tried to change ownership
and have been told I have no rights. I have also tried to import the
forms and again, was told that I don't have permission to do that.

Hmmmm.... any other thoughts? I appreciate them all!
Aliza
--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200807/1

Jul 26 '08 #9

This discussion thread is closed

Replies have been disabled for this discussion.