Is it possible to lock entry into a field based on the contents of another field?

For example: I have an "expense type" field. If this field has the word "kilometers" in it I don't want users to be able to enter data in another field.

The simplest would be to add an auto-enter (Replace) calculation to that field. Example, if field is called text:

If ( ExpenseType ≠ "kilometers" ; text )

In this way, a User can still enter something in the field but FM will nicely (silently) just remove it. This prevents the validation error which unnerves Users. Second method would be field level validation and third would be restriction through Access Privileges. Both of these methods are a bit harsh (from User perspective). If you go the Auto-Enter nice-removal way, be sure to uncheck 'Do Not Replace Existing Value for Field) in Auto-Enter tab (right below Calculated Value checkbox).

If you instead wish to try the other methods, let us know and we can explain them also.

LaRetta

Edited February 18, 200619 yr by Guest
Removed default result from If()

I broke one of my own principles here ... I neglected to consider the User experience. If I (as a User) kept typing into a field and the text just kept disappearing, I would feel a reaction and it wouldn't be positive! Therefore, I suggest one of two things:

1. Just place a soft grey text label above the 'text' field with words "Text not accepted if ExpenseType is kilometers"

2. Create a DisplaySorry (standard text) field with Auto-Enter (Replace) of: If ( ExpenseType = "kilometers" ; "Sorry, text not allowed. ^)" )

I felt I should mention it because it dawned on me that I have three fields which use this technique but all lack this respectful aspect. Users get jerked around enough by the electronics world - I don't want them to feel jerked around by MY program too.

LaRetta

LaRetta - Thank you very much for the tip. I will try this today.