How do I protect tables by direct update.

  • Thread starter Thread starter Sunny
  • Start date Start date
S

Sunny

I have created small application with few forms and reports. My tables are
on SQL server and I am liniking these tables in my ACCESS application. How
can I prevent all users to make changes directly on tables?

I tried to setup login form at startup and can't bypass the login form, but
after closing application if someone open the application again from File
menu, it wont open login form again and user can access tables directly.

This application is not in project, its just mdb file with front end objects
(forms,reports,modules,etc...) linked to SQL tables. Is there any other way
to protect tables by direct updation?

I am using Access 2003/SQL server 2000.

Thanks.
 
Sunny

Preventing users from "touching" the tables would require some serious
security (have you checked in the security newsgroup?).

Would it be enough to tell the users that if they work directly in the
tables, their application will fail? Then if they still do it, they get to
fix it?!

Would it be enough to simply make it harder for them to play in the tables?
If so, one approach might be to hide the database window, so they can't
easily see the tables directly. Or perhaps even hiding the tables...?
 
All of your security should be on the SQL Server database.

Otherwise, if you have a switchboard main form, then on
the OnClose event, add a DoCmd.Quit statement. That will
stop your particular scenario.


Chris Nebinger
 
Back
Top