Take a look at Tools>User and Group Permissions...
Have you thought of designing two different 'front ends' ?
That is seperate the data from the forms/code.
All (and only) the data is stored in one database and you have another database with all the forms/queries/reports etc
Then link the tables in the 'data' database to the 'front end' database.
This can be a good idea as if there are any problems with the front end database the actual data will not be affected.
I have personal experience of this. I created a database with the data, forms and (a lot of) code altogether. Only two or three people used it but after a while it became corrupt - couldn't even open it.
Luckily enough I was able to get a backup copy from the network folk. The only problem was it was about a week old. so I lost about a week's worth of data.
So I did as described above, seperated the data into it's own database.
