security

[andrew g]

i am currenty installing an access database on a network, and want to let
everyone view it and enter/delete data, but not change the settings of the
database (eg. change forms/database settings/etc. Only admins (myself and 1
other) should be able to actually edit the background database.

How is this done? i have read alot about users levels but don't totally
understand it.

Thanks for your help.

 

[Scott McDaniel]

i am currenty installing an access database on a network, and want to let
everyone view it and enter/delete data, but not change the settings of the
database (eg. change forms/database settings/etc. Only admins (myself and 1
other) should be able to actually edit the background database.

How is this done? i have read alot about users levels but don't totally
understand it.

You can deploy the database in the .mde format, which doesn't allow users to make design changes to
forms/reports/modules (note: they can make changes to tables and queries, if they can see them). As far as not allowing
them to change settings - a combination of various startup options would probably do this for you.

You can implement ULS, but it's not a trivial exercise.

http://support.microsoft.com/default.aspx?scid=/support/access/content/secfaq.asp

Thanks for your help.

Scott McDaniel
scott@takemeout_infotrakker.com
www.infotrakker.com

 

[Jan Kowalski]

i am currenty installing an access database on a network, and want to let
everyone view it and enter/delete data, but not change the settings of the
database (eg. change forms/database settings/etc. Only admins (myself and
1
other) should be able to actually edit the background database.

How is this done? i have read alot about users levels but don't totally
understand it.

Thanks for your help.