>
>There's a finite limit to what we can do to keep bad data out of a system. I have a number of systems that require the entry of length of feet. When a user types in 251, for example, I have to assume that's what they mean and not 125, or 152, or 521, etc. In your situation, prompting a user a second time, for example, just adds a level of annoyance. If it was done, they could just as easily get into the "habit" of responding Yes to the second prompt. What then? Add a third, then a fourth, ad infinitum?
>
>The best "habit" for them to get into is to actually "think" before responding. And I realize that in some cases, it's asking a lot.:-)

George, you hit it right on the head.

** PLease excuse the ranting/venting to follow *****

I have a severe problem with our users(thankfully it is just an internal application) taking NO responsibility for data entry errors. We have put more than enough validity and reasonableness checking coded into all data entry forms,(with more being added all the time) but still any application will be at the mercy of bad data entry clerks. I am invariably finding data related problems when users call with 'This program isn't working...'.

Add to this the fact that some processes they have to do are fairly complex, requiring multi-step operations on their part be performed in the correct sequence and the problem is worsened. I have added more and more audit logging over the years to deter people from lying about what they did, or did not do, and in what order. BLEAH!!!

A bit of primal scream therapy is appropriate at this point.... :)