Limiting Field Access

These are often asked questions regarding setting up a new FileMaker database system. "How can I limit when the user can enter data into the field?" Or, the alternative, "Once the user enters data, how can I make sure they don't change it unless I want them to?"

Both of these types of questions can be answered using a variety of methods. The core to understanding their answers is that there's really only only two methods for limiting field access. One is controlling the display of the field and the other is truly limiting access to the field data itself.

Using the knowledge in this video you should be able to come up with a method which fits your exact situation. The video walks through the use of the various options which FileMaker provides for limiting access to a field. If you'd like to know which options you should use to control access, then give this video a view.

AttachmentSize
LimitingFieldAccess.zip1.59 MB

Comments

So I go about things differently. I intercept keypresses with trigger scripts, so if the field is locked I simply don't let them get into the field, and if they do, well there's always the validation script to ensure it doesn't happen! My method is a little more involved but serves two purposes. It's second purpose is I have masks, I can get data in the format I want. If I name my field "Mask X30" then it will also ensure they type no more than 30 characters, it just beeps. I check the selected text too, so if you are at 30 but type something that would replace your selection then it permits it. I can use "Mask N9.2" to get up to 9 decimals followed by a point and two more places. I have multi-line too. It's a method that when done right means I can just name new fields with the right mask, set the trigger scripts (using a parameter to say if it's locked or not), and no further work is needed.

My users are fussy, they may not be allowed to modify something but they want to be able to copy the text.

Personally I think Filemaker would save us all a lot of time if they introduced data masks, almost everyone wants to get some form of number in a given format, be it a tax code, national insurance number, drivers number, etc. Us developers spend ages just making sure the right data is entered. A simple mask would be all that's needed! e.g. xx9999xx would take ab4321cd.

Hi Matt,

It's the 'magic' that bothers me. Why does a "Goto to Field" command work in a script and not in single step? For that matter, why does it even work at all if Browse Mode is disabled for the target field? Seems contrary to the field entry setting.

Mike