On 07/02/13 11:26 AM, Gene Wirchenko wrote:
HOWEVER, I do not design my forms in such a way that that is
likely to be an issue. The validation that the user would fall afoul of
is *just for that control*. I often have form labels stating the valid
input values where they are not obvious, and my error messages are the
same way.
Good point, Gene. Where I have a validation routine that will be used
for multiple controls, e.g., testing that a value is within limits, that
routine is a method of a business object, and the code in the Valid
method calls it with parameters:
Result = oBox.ValidLength()
or Result = oBox.ValidWidth()
That way, if the rules change you don't do it in the form.
Dan
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
