"Read only" front end

[SueBK]

I recently split my database into back end and front end to overcome a conflict caused by multiple users (learn something new every day). Now I'm wondering - can I create a front end version with everything locked against editing?

I have a very small team of data inputters, and a much larger team of data users. It would be handy to be able to give the users a copy of the front end and say "here's how you find info; you can't change anything; go for your life". Maybe then the pestering emails will dwindle off (we can all dream, can't we?).

My assumption is that I simple copy the front end; delete anything the users don't need; and then change the form properties to no edit, no delete, no new records.

It just seems a little too simple, so I thought I'd check it really is as obvious as it seems.

 

[Lightwave]

Sue sometimes this database stuff really is that simple... That would work.

You could also probably do it by putting the back end into an area on the network where users only have read permissions as well.

 

[spikepl]

You can do that. The alternative option is to set up some user management, so only the chosen ones can edit. The drawback is that you have to manage the users and to set it up in the first place. The advantage is that you only have one copy of frontend for development. Murphy dictates that sooner or later you will run sour in deleting and changing various settings, and either the readers' frontend will fail, or they will inadvertently get more rights than desired.

 

[DavidAtWork]

Just a word of warning if you're trying the "change the form properties to no edit, no delete, no new records". That will be fine if the users cannot get to the database window, if they can and are able to see the tables, there wouldn't be anything to stop them editing/deleting records that way in which case Lightwaves suggestion may be a better solution
David

 

[SueBK]

Thanks for the warning David. I don't think any of users would be interested in changing records delibrately. I'm more concerned about ensuring they can't accidently delete or modify information.
I assume in 2007 it's possible to create the front-end to open up without the database window showing. I know a previous database I've worked on opened up in a hidden view (drove me nuts as a programmer!)