Craig,
I agree with you on both points.
The advantage of good, universal, "background" error reporting is:
1. It helps pinpoint errors you've failed to trap (especially on
large, complex systems) and
2. You can provide immediate, meaningful help to users encountering
such errors.
Paul Looney
On Jun 10, 2009, at 2:46 PM, [email protected] wrote:
It seems far more important, and far easier in the long run, to
validate
entry data before it gets anywhere close to being mishandled. Check
to see if
numbers are numbers, dates are dates, etc. I would bet that the
errors fall
into a very few categories, and these can all be screened early on.
Many newbie (ahem) error posts are of just this type, for example, an
errant char in the second line of a field, and only the first line
is visible,
where the contents of the field has some math done to it. So
another level of
checking that I use all the time is to act only on line 1 of the
field that
purportedly has valid data in it. But even this should really be
vetted at
entry time.
Craig Newman
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
