Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / New Users / September 2004

Tip: Looking for answers? Try searching our database.

How do I protect tables by direct update.

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Sunny - 07 Sep 2004 17:22 GMT
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.
Jeff Boyce - 08 Sep 2004 12:10 GMT
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...?

Signature

Good luck

Jeff Boyce
<Access MVP

Chris Nebinger - 08 Sep 2004 15:19 GMT
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

>-----Original Message-----
>I have created small application with few forms and reports. My tables are
[quoted text clipped - 14 lines]
>
>.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.