Beginner Security (2k)

[officespacer]

Hi, This is my first week using access, and I just made a database for the company im working for to keep track of status of different items. There will be many different people using this database including people who will be reading the info only, some people will be updating PARTs of it, and people who can only view reports. am I best off using the wizard to set the access levels of access? or should I try to do it manually?

[HansV]

I would recommend becoming familiar with various aspects of Access a bit more before tackling security. Although it is not as complicated as many people think, it not really a subject for beginners.

Moderator <!profile=WendellB>WendellB<!/profile> has a tutorial on security on his website: The Secrets of Security. It contains an introduction and useful links; I recommend Microsoft's Security FAQ (the first link).

[officespacer]

I've gotten as familiar as possible in the time frame I've had... I really don't have much of a choice at this point, it has to get done for this week. Thanks for the link though, I'll go through it.

[Caesar3]

I'd like to share a few tips on this topic. I owe a debt of gratitude to HansV and many other fine people who work this forum, and this is one way I can repay their generosity. I was at the point you are not long ago. Re: security, here are some lessons I've learned here in the Lounge. (Nothing I'm writing can replace what you'll pick up from HansV or the tutorial he pointed you to...just FWIT.)

First, make sure you split your database into a front end and back end. The Database Splitter (Tools > Database Utilities > Database Splitter) does the job nicely. You'll then have your tables where the users can't readily get to them and wreak havoc. Then you can tailor your front-end components to suit the needs and abilities of the individual users. The split DB will also make it easier for multiple users to use the database at the same time.

In your forms, be sure to disable fields where you don't want the user monkeying around with the data. See the Properties sheet for the form, then find "Enabled" on the Data tab and set its value to No. Now the user won't be free to change the serial number for a part, for example.

Make sure users never, never get access to the tables themselves. Those tables need to reside in a "holy of holies" where only you, the high priest (or someone like you) can go. Even otherwise intelligent people can make stupid mistakes in a database, especially if they think Access is just like Excel, only more complicated. You may have someone like I had to deal with who insisted on using the tables

[SteveH]

In addition to Lucas's points you might want to take a look at <!post=this thread ,195604>this thread <!/post> and the handouts on it. They might help you avoid a few of the more common pitfalls.

<img src=/S/cheers.gif border=0 alt=cheers width=30 height=16>

[Caesar3]

Wow! I wish I'd seen this thread back when I was starting! Great stuff, and easy to understand! Thanks, Steve!