use a field set to 0 or 1 and set locked (1) unlocked(o) with privilege set if field=1 of a record dont allow edit
Thank you I will work on this. Much appreciated as my users are accidentally changing the meeting numbers.....
You could stack 2 versions of the field, one not enterable except in Find Mode, the other set to Hide when:
not isEmpty (self)
This leaves it enterable until the value is entered, and in Find Mode, otherwise its read only. No permission requirements involved.
You might need some scriped method if there is ever a need to change or correct that data.
Thank you, I will look into this as well. I will leave this post open for a while until I can actually work on it. Got busy here all of a sudden at work and we are expecting a snow storm today so may head home.
So I have figured out how to protect the meeting # field in the main layout that it usually gets accidentally changed in.....
When a user creates a meeting it is done in the meetings log layout so they can see all the previous meeting numbers and set the next meeting number correctly and sequentially. They then select a button that takes them to the meeting details layout where they fill in various info about the meeting, (date, attendees, etc.) And the meeting # is also on that layout so they know that they are on the appropriate meeting site..
Anyway, in the inspector I deselected the Field Entry, Browse in the behaviour section. So the meeting number can be corrected if need be in the log layout.
thank you all for helping to get my thinking cap on
All answers in this post are correct and will give you food for thought