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 / Security / February 2005

Tip: Looking for answers? Try searching our database.

Restricting to view the design

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
shobha - 25 Feb 2005 14:59 GMT
Hi All,

I'm trying to restrict the user from viewing the design of my table,
queries, forms and reports but i'm not able to. Any suggestions regarding
this is highly appreciated.

Thanks
Shobha
Rick B - 25 Feb 2005 16:31 GMT
Have you tried searching for your answer?  This is a very common question.

> Hi All,
>
[quoted text clipped - 4 lines]
> Thanks
> Shobha
Jeff Conrad - 25 Feb 2005 16:43 GMT
> I'm trying to restrict the user from viewing the design of my table,
> queries, forms and reports but i'm not able to. Any suggestions regarding
> this is highly appreciated.

If you distribute MDE files, your users will not be able to open forms,
reports, or modules in Design View. They would not be able to mess
with your code. I also strongly suggest setting limited options under
Tools | Startup. Hide the Database Window, disable the Shift key
bypass, etc. To protect the design of tables and queries your best bet
is to implement full blown Access User Level Security (ULS).
You would then deny all permissions on the tables themselves and create
RWOP queries for the users to access the table information. Assigning
appropriate permissions to various database objects would also be needed.
The users could still possibly import the queries into another container,
but they would essentially be worthless since they would not be able to
access the data in the BE file.

If you have never used ULS before, be prepared for a lot of work ahead
of you. ULS is not a trivial undertaking at all so I would recommend
ALL of the following reading material before beginning. Also, practice
on dummy databases until you are really comfortable with it.

Access User-Level Security:

Security FAQ (the Security Bible):
http://support.microsoft.com/?kbid=207793

Jack Macdonald's Security Document:
http://www.geocities.com/jacksonmacd/AJMAccessSecurity.pdf

Lynn Trapp's Ten Security Steps:
http://www.ltcomputerdesigns.com/Security.htm

Joan Wild's Tips:
http://www.jmwild.com/security02.htm

The Security Whitepaper is also worth reading:
http://support.microsoft.com/?id=148555

Keith Wilby's Instructions (See step-by-step link)
http://www.keithwilby.com/

Other Good Information:
http://www.access-experts.com/default.aspx?selection=TutorialSecurity&sm=18

Other Microsoft KB articles of interest:

Description of how to help protect a Access 2000 database:
http://support.microsoft.com/?id=254372

Description of the role of workgroup information files in Access security:
ACC97: http://support.microsoft.com/?id=303941
ACC2000: http://support.microsoft.com/?id=305541
ACC2002/2003: http://support.microsoft.com/?id=305542

Good luck,
Signature

Jeff Conrad
Access Junkie
Bend, Oregon

 
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.