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 Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Making Read-Only Front End

Status
Not open for further replies.

FeS2

Technical User
Aug 16, 2002
82
US
I am setting up a new front end for a database but need to make that front end unable to make any changes to the data/records in the back end database.

I looked at Security but do not want to have to make the people using this front end log in. I want them to be able to make new queries or forms, but to never change the records.

Is there a fast easy way to do this?
 
Try the database splitter. Once you've completed your database run the database splitter. It will put all of your tables in a backend database and your main db will be linked to them. Users cannot delete any records using the main db.
 
Ummmm - I maintain dozens of split databases and regularly add/update/delete data in all the linked tables from the frontend. You can't fiddle with the table structure from the FE, though. Could be because I have admin rights?

"Rome did not create a great empire by having meetings, they did it by killing all those who opposed them."
 
Genomon, you're right, don't know what I was thinking.

FeS2, the security is not that hard to setup. You can create one login account that everyone can use without needing a password.
 
FeS2,

You can use security.

Things to note that make it easy...

The Admin user and the Users group are common to all workgroups. By default everyone logs into the default workgroup using Admin with a blank password.

So any permission you give Admin you are basically giving to the default log on.

You can set the permissions in a front end table to not be able to update the backend. The caveat here is it is not that difficult to see where the backend tables are so savy users could find it and update it anyway. It is best practice to set the permissions on the backend tables and leave the frontend tables wide open.

Also noteworthy is that Access security is fundamentally weak.

Keeping all this in mind you should be good.
 
I left something out...

By default Admin is a member of the Users Group. This means you have to remove permissions from both.
 
Great, thanks for the replies.

I was able to use the Security built into Access to limit the record updates but allow the users to create new forms and queries, also with it set to no password, it can be given to new users and they get the same restrictions without having to memorize another password.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top