Ownership of Database.mdb file

  • Thread starter Thread starter Marvinator
  • Start date Start date
M

Marvinator

I want to secure a database from people being able to change the layout
or design. I've set up a unique Administrator account and reassigned
all ownership over to this new account. (Deleted the old Admin from
the Admin group, too.) However, the problem remains that the database
object is still showing owned by the Admin Account.

My thought is to create a new User and delete the Admin completely. So,
of course, I"m asking 'is this a good thing to do'? If not, then how
can I make sure that the users cannot change the layout in anyway.
(Most importantly, since i plan on selling this database, I don't want
anyone to remove any of the Copyright notices or my name and resell the
database.)

Lastly, Is this really the way to secure the database? Someone here in
the office made the comment that they could just as easily rename the
file and delete the .mdw file and reclaim ownership of the database as
well as control of all objects. Is this something to consider?

THANKS!!
 
Marvinator said:
I want to secure a database from people being able to change the
layout or design. I've set up a unique Administrator account and
reassigned all ownership over to this new account. (Deleted the old
Admin from the Admin group, too.) However, the problem remains that
the database object is still showing owned by the Admin Account.
Click to expand...

There is more to securing a database than that. It sounds like you missed
the very first step, to create a NEW workgroup file. You've just modified
the system.mdw workgroup file, which is common to everyone who owns Access.
It would be trivial for anyone to get back full control.
My thought is to create a new User and delete the Admin completely.
Click to expand...

You'll find that it is impossible to delete the Admin account completely.

You need to follow every step, in the proper order, to secure your database.
Download and study the Security FAQ
http://support.microsoft.com/?id=207793

Security Whitepaper
http://support.microsoft.com/?id=148555

Although the whitepaper is old, it contains information to help you
understand security.

I've also outlined the detailed steps at
www.jmwild.com/AccessSecurity.htm
 
Forgive me if I was unclear. I have created a new .mdw file.

I will study the faq a bit more and see what I can find.
 
That's good, re the new mdw file. You missed the step of creating a new mdb
while logged in as your superuser and importing all the objects - that is
the way to ensure that all objects are owned by that user (not via the
dialog).
 
On 9 Feb 2006 06:03:12 -0800, "Marvinator" <[email protected]>
wrote:

[snip]
Lastly, Is this really the way to secure the database? Someone here in
the office made the comment that they could just as easily rename the
file and delete the .mdw file and reclaim ownership of the database as
well as control of all objects. Is this something to consider?
Click to expand...


Only if it's not secured properly. If the file is secured properly,
those steps will not work.

Bear in mind that Jet security is sufficient to keep out casual and
somewhat knowledgeable snoops. It is not sufficient to stop a
determined hacker from doing whatever they want with your file. That's
the nature of a file-based database system.

**********************
(e-mail address removed)
remove uppercase letters for true email
http://www.geocities.com/jacksonmacd/ for info on MS Access security
 
Back
Top