>>we place the test for leaving a required field in the save button. it's a bit too detailed for here (checking all objects to see if they require an entry, warning if left empty and returning to first object failing), but if you want more, let me know.
>>
>>if you leave the test in the field's valid, you can't leave until something valid is entered...
>
>The save button method has been considered but was thrown out by
>the user/data entry personnel as annoying in this senario:
>
>Suppose you have a entry operator who made 10 mistakes on a 20
>field screen. When they press save I inform them that this field was in
> error and place them back onto it, when they fix the problem they press
>save and are given the same message and placed on the next error
>field. This continues until all 10 are taken care of. They requested
>that they be informed as soon as possible of problems. That is when
>they leave a field, but that brings up the problem I needed help on.
>If there was some way checking to see if the cancel button was pressed
>then I could let them out of the screen.
>
>Thanks for replying though
>
>Bret

our solution handles all ten at the same time.

ps if that's their biggest concern, fire the data entry person and replace w/ someone who needs a job and will work.