Securing a database

[Pele]

I have put together an application in Access and we are
now going to be sending it out to the field for our
customers to use. I need to prevent changes to the design
of this tool and prevent users from seeing the code behind
the tool. But whatever security solution I implement,
should allow macros in the tool to be able to select,
delete and copy tables.

I tried to use the Security Wizard in Access 2000 but I
don't think I understood that enough. I then went and
created Users. I created one User (TACADMIN) and put him
in the Admins group and I created another User (TACUSER)
and put him in the User group. They both have seperate
passwords.

The problem is that Access still keeps on logging me on
under the default Admin User name since I was the one that
created the database. I'd assumed that Access will give me
a choice as to which of these 3 available users I wanted
to log in on but it doesn't.

Can somebody help me. I have a clean copy of the
application and I try any suggestion on a copy of that.

Pele

 

[Gabe]

When you say Access didn't give you a choice of names to
use, you mean you were expecting to see a drop down menu
of names? My experience has been that you have to type
in the name you want to go in under (remember it is case
sensitive)

 

[Pele]

Gabe,

I realized later that I didn't use the wizard correctly
the first time and that was why I wasn't being prompted. I
cleaned up a few things and tried using the wizard again
and this time it was prompting me like you mentioned.
Thanks for your help.

Toks

 

[Joseph Meehan]

I suggest you start by reading
http://support.microsoft.com/default.aspx?scid=kb;[LN];207793

Access security is a great feature, but it is, by nature a complex product
with a very steep learning curve. Properly used it offers very safe
versatile protection and control. However a simple mistake can lock
everyone including God out.

Practice on some copies to make sure you know what you are doing.

You should consider using an MDE file, just save as and MDE file. I
believe that may do everything you want a lot easier.