Security

[lead 27]

Hi again

The security on my database so far is justthe standard everyone has a user name and a password, no one can alter the design of a form apart from me

I am just wondering if there is any way that I can prevent people viewing and altering tables, queries etc. It would be good if when the open the database the main form comes up so they can navigate from that and they are always taken back to this and they can never see the database window

Does this have anything to do with front end and back end databases?

Sorry its a bit vauge but hopefully you will know what I mean

thanks

 

[Bob Miller]

Hi again

The security on my database so far is justthe standard everyone has a user name and a password, no one can alter the design of a form apart from me

I am just wondering if there is any way that I can prevent people viewing and altering tables, queries etc. It would be good if when the open the database the main form comes up so they can navigate from that and they are always taken back to this and they can never see the database window

Does this have anything to do with front end and back end databases?

Sorry its a bit vauge but hopefully you will know what I mean

thanks

The simplest way is to use Windows permissions. Have your IT give you owner permission on the BE's folder. That way you can assign users permission as you see fit. That was the way I controlled security on a multitude of dbs I had written for my company. There was a Personnel folder to which only Personnel employees had access, a Lab folder to which lab and certain production employes had access, etc. As a matter of fact, I actually had a complete server that I "owned."

 

[boblarson]

Just so you are aware, you can implement Access security to do what you want and the suggestion about Windows permissions is a bit misleading, as far as Access goes.

There are no Windows permissions that you can set to limit someone to be able to alter tables or queries. Windows security is only limiting on the file level, not what is inside the mdb file. So, you would need to implement Access security (first make a copy of your database file so, if anything goes wrong, you haven't hosed yourself).

Just run the "User-level Security Wizard" that is under Tools > Security and it should lead you into your security. Then, you will need to go into the users or groups and edit the permissions.

 

[Bob Miller]

For what he wanted, Windows permissions are the easist to implement. He said he wants to "prevent people viewing and altering tables, queries etc." The easist way to do that is to keep them out of the db period. Viewing table data is the most basic function of a db. If I'm wrong about that, please explain why.

 

[Banana]

I am pretty sure that if you were to restrict the file permissions on the back end, you would be effectively making the database totally unusuable as all users require a complete permission to access the backend (after all, they *do* write, read and modify the backend data).

I'd agree with Bob Larson that Access security is pretty much the answer, not Windows permissions.

Lead 27, try and search the forums about securing the database, setting permissions. Posts by Pat Hartman and The_Doc_Man are by far most informative.

HTH.

 

[boblarson]

For what he wanted, Windows permissions are the easist to implement. He said he wants to "prevent people viewing and altering tables, queries etc." The easist way to do that is to keep them out of the db period. Viewing table data is the most basic function of a db. If I'm wrong about that, please explain why.

If you notice his post again, he says he wants them out of the tables and queries, but they are also using the database (see how he says that when he mentions them opening the initial form). And, as Banana has mentioned, if you lock them out of the folder, you lock them out of the database - period. The users of the database need Read/Write permissions to use the database.