Just protect backend

[DMW]

I have a split database which mult. users will access. I
use forms to get them through the program and hide tables
etc while they are there. I just want to be able to put a
password on the backend of the database so that they can't
directly open and change it or add data . I don't mind
changes and updates through the controlled forms.
Can I do this without requiring each user to sign in with
a password to use the application? Thanks in advance for
your advice.

 

[Scott McDaniel]

You can set a Database Password on the BACK END, but they will have to enter
this password (unless you have used unbound forms and can code it into your
connect string) ... should have to do it only once per session, which isn't
really a big deal.

 

[Jack MacDonald]

You can deny the Admin user permission to open the tables in the
backend. Then use Read With Owners Permission (RWOP) queries in your
frontend to access the data. It's explained in the Security FAQ - it
is linked from the site in my signature.

I have a split database which mult. users will access. I
use forms to get them through the program and hide tables
etc while they are there. I just want to be able to put a
password on the backend of the database so that they can't
directly open and change it or add data . I don't mind
changes and updates through the controlled forms.
Can I do this without requiring each user to sign in with
a password to use the application? Thanks in advance for
your advice.

=======================================================
Jack MacDonald
remove UPPERCASE LETTERS from email address
Vancouver, B.C. Canada
Info about MSAccess user-level security
www.geocities.com/jacksonmacd