Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Difference between field and record validation
Message
From
18/04/2009 09:34:14
Hilmar Zonneveld
Independent Consultant
Cochabamba, Bolivia
 
 
To
17/04/2009 12:20:24
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Environment versions
Visual FoxPro:
VFP 9 SP2
Miscellaneous
Thread ID:
01395230
Message ID:
01395427
Views:
53
>As a user I prefer feedback on incorrect data input to be as soon as possible, not after I have keyed in a number of other fields. As long as the field validation does an immediate check for the Esc key, bailing out if it was pressed, the user is not trapped in the field with no way out.
>
>And as an end user, I do not want to be nagged incessantly {s}. I prefer to have all the validation occur when I try to save the data and be presented with all the problems at the same time so that I can fix all of them in one fell swoop.

That is exactly what I have done at Bata/Bolivia.

For convenience in programming, I have most rules in a table. A validation function, "RecordValid([tablename])" will evaluate all the rules for the specified table. "Table" is really a "set of rules", to be precise - but in most cases there is a one-to-one correspondence between the two.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
Previous
Reply
Map
View

Click here to load this message in the networking platform