Wrox Programmer Forums
|
Access Discussion of Microsoft Access database design and programming. See also the forums for Access ASP and Access VBA.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the Access section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old January 27th, 2004, 06:43 PM
Friend of Wrox
 
Join Date: Jul 2003
Posts: 128
Thanks: 0
Thanked 0 Times in 0 Posts
Default Read-Only Access

Hi All Experts!

I have a database with a form and some reports. This form allows user to enter certain criteria to get reports that they want. What I want to do is to somehow lock the database. So when the user click to open the database, they will only see the form and nothing else; they CANNOT do any editing, updates, creates tables, etc. Please tell me how can I do this task.

Thank you for all your help!

Leon

 
Old January 28th, 2004, 12:19 PM
Authorized User
 
Join Date: Dec 2003
Posts: 81
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Do you mean that they only see the form when opening the DB. If so, use the on start menu to degignate the form they can view. If necessary, you can hide the other components of the DB, You'll also want to set the form to view only so no changes to the table can be made.

What type of report are you running...have you considered a paramater query instead of using a form??

Hope this helps

John
 
Old January 28th, 2004, 12:33 PM
Friend of Wrox
 
Join Date: Jul 2003
Posts: 174
Thanks: 0
Thanked 0 Times in 0 Posts
Default

I would suggest implementing security, thereby not allowing them to make any changes, only run reports as specified. Granted, it's not a simple task, but worth it if your data and database is worth preserving.

Regards,

Beth M
 
Old January 28th, 2004, 01:51 PM
Friend of Wrox
 
Join Date: Jun 2003
Posts: 1,151
Thanks: 2
Thanked 14 Times in 14 Posts
Send a message via ICQ to SerranoG Send a message via AIM to SerranoG
Default

If you want a really secure database, then as Beth said it can get quite involved... but there are a couple of things you can do to make it somewhat secure from all novice Access users. The experts, of course, will always get around these suggestions.

First and foremost make a back-up of your database before you implement security. In that way if you lock yourself out of it, you'll have the back-up.

Suggestions:
  • Turn the MDB file into an MDE file. Click TOOLS > DATABASES > MAKE MDE FILE. This will strip all code from your forms and reports and will not let people edit the forms and reports.
  • Click TOOLS > STARTUP and UNselect those checkmarks for selections you don't want people get access to. Read up on them first so you understand what each means.
  • Separate your data (back end) from your forms and reports (front end). Give each user the MDE front end and put the tables and queries (back end) in a spot where the file is read-only. Have your front end link to the back end using the Linked Table Manager.
These suggestions are low to medium security measures. For a really secure database, someone else will have to provide details. I've never had to secure anything that badly.


Greg Serrano
Michigan Dept. of Environmental Quality, Air Quality Division
 
Old January 28th, 2004, 02:08 PM
Friend of Wrox
 
Join Date: Jul 2003
Posts: 174
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Just for clarification purposes, in Greg's bulleted points, I would separate the data into the backend before you convert a database into an mde.

Also, if you wanted to learn more about security, search M$ Knowledge Base for MS Access Security FAQ then read it, read it again, and then reread it. Also, for another layer, if your backend is on a sql server, you can also implement security at this level.

Regards,

Beth M
 
Old January 28th, 2004, 05:22 PM
Friend of Wrox
 
Join Date: Jun 2003
Posts: 1,151
Thanks: 2
Thanked 14 Times in 14 Posts
Send a message via ICQ to SerranoG Send a message via AIM to SerranoG
Default

Good point, Beth. Yes, if you're going to do all three, do the bullets in reverse order that I gave you. The MDE file and the UNchecking of options bullets should be done to the front end.

Greg Serrano
Michigan Dept. of Environmental Quality, Air Quality Division
 
Old January 28th, 2004, 05:27 PM
sal sal is offline
Friend of Wrox
 
Join Date: Oct 2003
Posts: 702
Thanks: 0
Thanked 0 Times in 0 Posts
Default

If all you need is a read only database for users, do not use Access security. Create a front end for the database which contains thereport andform that ou need. Link the table and then create an mde file. Use ado if you can to avoid linked tables.

Access security sucks and brings a lot of problems. One of them is performance degradation. Specially with split databases.

Remember K.I.I.S.





Sal
 
Old January 28th, 2004, 05:33 PM
Friend of Wrox
 
Join Date: Jul 2003
Posts: 174
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Sal,

I would tend to disagree with you on this one. Although I haven't posted as many times as you on the boards, I know my application. Access security doesn't 'suck'. You just need to know what you are doing and implement it correctly. It isn't for the newbie to create an app, apply security and expect everything to work right the first time.

Respectfully,

Beth M
 
Old January 28th, 2004, 05:39 PM
Friend of Wrox
 
Join Date: Jul 2003
Posts: 128
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Thank ALL for all your helps! I am very glad there are awesome people like your guys/ladies out there willing to spend your time to help me out! Your comments/suggestions are greatly appreciated!

Leon

 
Old January 28th, 2004, 06:02 PM
Friend of Wrox
 
Join Date: Jul 2003
Posts: 128
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Hi John,

I think you have just the answer that I am looking for; I do want only see the form when openning the DB. However, I can't find how to do the "on-start" method you are referring to. Can you please tell me which menu or method to do this on-start? Also, I am using parameter query; where users can enter a criteria and a report will pop up based on the criteria/parameter they have entered. Even with this parameter query, I still want them to only see the form and now able to change anything.

Thank you.

Leon


Quote:
quote:Originally posted by jrwlkn
 Do you mean that they only see the form when opening the DB. If so, use the on start menu to degignate the form they can view. If necessary, you can hide the other components of the DB, You'll also want to set the form to view only so no changes to the table can be made.

What type of report are you running...have you considered a paramater query instead of using a form??

Hope this helps

John






Similar Threads
Thread Thread Starter Forum Replies Last Post
Access 2000 Read-Only Problem sanjna000 Access 1 May 15th, 2006 01:13 PM
Read MSWord From Access? tonyrosen Access VBA 3 November 9th, 2005 02:46 PM
Why use VB.Net to read Access? AmyEL VB.NET 2002/2003 Basics 3 February 24th, 2005 12:12 PM
ASP to read .CSV into Access liquidmillsap Classic ASP Databases 1 January 4th, 2005 11:01 AM
How to read/write Access Database jmmendes Access VBA 0 November 18th, 2003 01:26 PM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.