Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Stop users from interfering with the database 4

Status
Not open for further replies.

mobile2

Programmer
Dec 19, 2002
38
GB
I am developing a database. It does not have user-level security. It is protected by a number of passwords into different forms. The users have to type in a password before the database automatically opens a "Navigation" form. I thought about removing the menu bar from this form, but realised it would take ages to do on every form and report. I do not want to remove all the options as some people like to have the "Window" option available so they can jump back & forward from different forms. The best option I can think of is, when prying users try and view the actual database from the window option on the menu bar it asks them for another password. I thought this would be a pretty common question but couldn't find any solutions on help. The thing is I regularly go into the tables, so don't want to make it too complicated to unsecure. I would be very grateful if someone has an easy solution so I can protect the tables, queries, reports, etc.

Thanks very much
 
I'd suggest implementing Access security. I'm not a big fan of the "home grown" security solutions.

Access security works pretty well, if you implement it correctly. To implement security, you need to follow all the steps correctly.

There's a security FAQ that should lay it out pretty well for you. The basic steps are:

1. Create a new workgroup using WRKGADM.EXE. Don't just make a copy of System.mdw.

2. Join the new workgroup.

3. Create a new user name for yourself, and set a password for your user name. Put your user name into the "Admins" group.

4. Remove the default "admin" user from the "Admins" group (leave them in the "users" group).

5. Open your database and run the User Level Security Wizard. This will make a secure copy of your database without changing the original.

6. Open the new, secure database, and set up your user and group accounts. If you don't want the default user to have access to your database, set up a new user group, and remove all permissions from the existing user group.

This is the condensed version of Access Security. I recommend you read the instructions so you understand it before you implement it.



 
If you want to eliminate the ability for users to access the table, design, etc. views then there are a couple things you can do:

On the Tools > Start-Up menu uncheck the Show Windows Bar.

Yopu can add the following code to the On open Event of your main Swtchboard or Form:

DoCmd.RunCommand acCmdWindowHide

However, any user that learns about the SHIFT by-pass or the F11 keys can still get into design view.

If you are interested in a db to solve this problem send your e-mail and I will forward you a copy.

"I know what you're t'inkin', ma petite. Dat Gambit... still de suave one, no?"
 
If you want to eliminate the ability for users to access the table, design, etc. views then there are a couple things you can do:

On the Tools > Start-Up menu uncheck the Show Windows Bar.

You can add the following code to the On open Event of your main Swtchboard or Form:

DoCmd.RunCommand acCmdWindowHide

However, any user that learns about the SHIFT by-pass or the F11 keys can still get into design view.

If you are interested in a db to solve this problem send your e-mail and I will forward you a copy.

"I know what you're t'inkin', ma petite. Dat Gambit... still de suave one, no?"
 
I would like to know more about stopping users use the shift by-pass & F11.

Thanks again

lyn.drysdale@ros.gov.uk
 
mobile2,
I second GDGarth's suggestion of using user-level security. It's a good system once in place.

jfgambit,
I recommend finding a place to post this database online before you get 10,000 requests for emails.

To those of you who will request emails from him,
I believe there are some FAQs on here somewhere describing how to disable the shift key and F-keys also.

I'm just trying to head this off before we get another 150+ post thread where the real information is lost among posts of "My email address is..."
 
KornGeek, GDGarth and jfgambit,

I would feel happier myself learning how to set-up the user-level security and do it properly but I'm also excited about trying out the control.mde.

Thank you all for your input

 
I have a question for you in response to GDGarth's post

If you apply those steps it makes a workgroup, but that workgroup gets applied for every database on the system. Is there a way to do it so the workgroup users and password only work for that one database that I am trying to build ??

I created a workgroup with all the users & passwords but all the usernames and passwords are applied to every database I have on my PC, any suggestions anyone ??

Thanks for the help
 
JaySang,
rejoin the original system.mdw file. Then, create a shortcut to your new database that links to your new mdw file. This will result in your system using the standard mdw, and only your new database using the new mdw.
 
If you don't want the new workgroup as default, open up WRKGADM again and set the original system.mdw file as your default workgroup. Then to open the special workgroup, use a shortcut to open your database with the command-line parameter "/wrkgrp c:\fullpa~1\path\filename.mdw".



--
Find common answers using Google Groups:

Corrupt MDBs FAQ
 
thanks for the quick reply!!

I created the shortcut, but it gives me an error message that you don't have the proper permissions

The shortcut I tried is:(in the target line)

c:\system.mdb c:\system_secure.mdw is this right ?

I also tried

c:\system.mdb =c:\system_secure.mdw any suggestions ?

thanks
 
Here's an example of one of my shortcuts:
Code:
"C:\Program Files\Microsoft Office\Office\MSACCESS.EXE" "C:\atemp\dev\rq_local_fe.mdb" /wrkgrp "C:\atemp\dev\rq.mdw"
 
JaySang,
You need to use /wrkgrp as shown in foolio12's examples.
 
I have another question :)

is their a command or function I can create to get who the current user is logged on. I need this for audit trails, so I know who modified or created a record ?

Thanks for all the quick help
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top