I am trying to prevent editing of records in browse mode. I set the file to be opened in read-only access mode. That prevents editing of records. I also made two buttons named Edit and Commit. Basically they have re-login scripts attached to them that will re-login the user without a dialog between read-only and data-entry access modes. The reason is as I will have quite a few people browsing the records daily so I want to prevent accidental changes of data.

When in read-only mode I would however like to get rid of annoying "your account level does not allow this action" message and I would like to lock the fields so that they cannot be selected much like field behavior setting.

Is it possible to lock all fields in the file via script so that they cannot be selected and make them selectable with another script (would attach that to my Edit button).

How would I accomplish that and is there maybe a better way of doing what I described here?

Thank you.,

Only using multiple layouts -- one set of layouts has fields limited to entry in find mode. It can be a lot of work.

There are better ways to lock/unlock records than re-login, especially since the password is embedded into the script, it will break when the passwords change.

Look into setting record-level acces privileges. I've used a system where records are "unlocked" when the record ID is entered into a global field. Records can only be unlocked one at a time, which solves the accidental deletion on records problem too.

Be aware that such a record locking system makes all scripted "background" processes that edit fields liable to break, because the records will be locked. This can be worked around by running the scripts with full access privileges, but then all info about the user that edited the records will be incorrect.

Edited July 12, 200718 yr by Guest