Cannot delete user "Admin"

I'm using Access 2000 (9.0.3821 SR-1) under Windows 2000

MS Access Help tells you that in order to secure a database, you need to get rid of the default user "Admin", as otherwise anyone with a copy of Access can open the database.

I followed the steps in the help file and
- created a workgroup file
- created a new user "newadmin" and added it to the "Admins" group
- imported the database into a new one so the owner is now "newadmin"

I then opened the database and made sure that
- I'm using the right workgroup file and
- the current user is "newadmin"

When I try to delete "Admin" from User and Group Accounts, following message comes up:

"Cannot perform this operation"

Also, although "Admin" hasn't got any permissions whatsoever, the database can be opened and changed if a different workgroup file is being used.

Any help would be appreciated very much.

avaturaAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

wsteegmansCommented:
You did the right thing. Create a new Admin-user, and delete all permission of the real admin Access-user.
You can't do more ... The user admin in Access is the default user and is always there in a DB. So, you can't delete it.

But, like you did, you can remove all permissions, so you can't use the account anymore (also be sure your admin user has a password!)

Regards!
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jadedataMS Access Systems CreatorCommented:
Hey avatura!

  Be sure that you fully understand the implications of "Locking Down" your mdb in this manner.

  If you lose the password, you're toast.
  If you leave the project and the next developer can't find the password, he/she's toast.
  If you leave the project and the customer can't find the password, their toast.

  Security at this level is not always a good thing...

regards
Jack
0
ornicarCommented:
----------------------------------------------------------------------------------------
This question has been abandoned and needs to be finalized.
 You can accept an answer, split the points, or get a refund (information at http:/help.jsp#hs5)
  If you need a moderator to help you, post a question at Community Support (http:/Community_Support/)

PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER!

ornicar
Cleanup Volunteer

---------------------------------------------------------------------------------------------
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.