Database Input Validation
bobsneidar at iotecdigital.com
Fri Jul 10 18:41:46 CEST 2015
IMHO, there are times when validating on closeField is useful, but if it is the only way you validate, it can also be a frustration to the end user. Lets say the user enters the name in an email address, but forgets what the domain part is. He goes to navigate to his email program, and Livecode barks at him about not having the correctly formatted email address. On the other hand, I use closeField to populate other fields as in my IP Calculator.
Also, be sure to skip validation for empty fields so the user has a way to get out of the field.
On Jul 7, 2015, at 01:19 , Pascal Lehner <tate83 at gmail.com<mailto:tate83 at gmail.com>> wrote:
Hi Peter and Bob,
Thanks for your ideas.
I think I found a good way by doing a input check for the user fields on
closeField to avoid totally wrong information and then I will store this
unicode encoded in the database.
This should avoid quite a few problems from the start.
More information about the use-livecode