Hi Marty,
In this case, I wonder how the value could exceed a tolerable range at all. Is it because at some point, the data can get into lookup table without constraints? I think you might have a bigger issue at work here; some business or data rule is being stepped on at some point in the process.
It's like a train wreck...a good error handler is like providing some nice, fluffy pillows so no one gets hurt but what you really want to do is find the break in the tracks :-)
>Good point John. I agree 100%. I wasn't clear in my example about the value being checked. It's not an input value, but a lookup value from a table. The user
cannot modify the lookup value from the module I'm working on. Since I can't fix the value, I'm considering throwing the whole mess over to the error handler, instead of writing custom "The xxx value is too high, contact the manager of yyy system." messages.
------------------------------------------------
John Koziol, ex-MVP, ex-MS, ex-FoxTeam. Just call me "X"
"When the going gets weird, the weird turn pro" - Hunter Thompson (Gonzo) RIP 2/19/05