How do I secure an Access 2000 database

[Guest]

I'm being forced to use Access 2000 to create an app. I want to secure it as
much as possible. I have unchecked the special keys and converted to an MDE.

I am surprised to find that I can open the MDE, open the tables, modify the
tables and change them. The only thing I can't get to is the code.

Is there anyway to secure it further?

 

[White Bilky]

I'm being forced to use Access 2000 to create an app. I want to secure
it as much as possible. I have unchecked the special keys and
converted to an MDE.

I am surprised to find that I can open the MDE, open the tables, modify
the tables and change them. The only thing I can't get to is the code.

Is there anyway to secure it further?

Yes, can invoke user-level security but you would need to invest a lot of
time and effort into learning about it.

There's a link to the Access FAQ on security on my web site along with a
step-by-step example. Be sure to fully understand the FAQ before you do
anything to your files and to back them up first.

HTH - Keith.
www.keithwilby.com

 

[Guest]

I do not know if you got an answer to this but this can be a very involved
process depending on what it is you are actually trying to accomplish.

All objects are created under the admin group and account in MSA, you must
change this if you do not want other being able to do this. This group and
account exists in all copies of MSA regardless of version and if you do not
change it, users can just copy it to another location and use the default
admin group and user to do what they wish.

MSDE is really just SQL and can be secured in much the same way. Now adding
in the MSA spcific security measures is another matter.

But you must remember that MDB and MSDE has a 10 user connection limit and
if you are planning to use this in a larger group then you really need to
rethink this.

If it is going to be something that will be ported / sitting independently
on individual user machines, you will have to rethink this.

There is a directory structure you should implement: UI, Code and data must
not be in the same container and must be secured using slightly different
approaches.

Everyone will have read on the tables and they can open them directly if you
do not restrict this. Even in the linked version they will be able to do this.

If you properly secure the containers individually, though they can try to
get in and mess with the tables, the design changes will not take.

Have a look at the following.
INFO: MSDE Security and Authentication
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q325022

Choosing and Using MSDE 2000 as the Database Engine for Your Application
(Microsoft Data Engine (MSDE) Technical Articles)
Learn the features and benefits of MSDE 2000, and see links to useful
information, including online documentation, Microsoft Knowledge Base
articles, and Microsoft white papers.
http://msdn.microsoft.com/library/en-us/dnmsde/html/msderoadmap.asp