Both methods have several advantages and disadvantages -- i.e., script validation in QuerySave/Script Library, "centralized validation code" in script library, flexibility and complexity of Lotus Script validation, ability to turn off all validation during testing/coding by remarking a single line, traditional validation formula, simplicity of formula language, native support of validation by the Notes UI, evaluates during refresh as well as save, ease of troubleshooting code....
So, you can see how I am going back and forth. Do you have any insight?
A single validation event allows you to present the user with all of the validation errors at one time. In a number of applications, we have set indicators near fields with invalid values with details on why the validation error occurred, as well as a consolidated list of all validation errors on the form.
Do you have comments on this Ask the Expert question and response? Let us know.
Dig Deeper on Lotus Notes Domino Application Development
Related Q&A from Brian Mahoney
Find out what types of calculations can be computed for a column in a Lotus Notes view and the best way to go about it with this expert response. Continue Reading
Find out why you can't use Formula language to include a doclink to a specific Lotus Notes view or database and need to use LotusScript instead. Continue Reading
Discover the reasons behind a Notes/Domino admistrator having trouble with disabled options in the "customize this view" section of his Lotus Notes ... Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.