>>>we have a few forms here with several objects that are validated at a the object level.
>>>the problem is, is that the user cannot cancel without the validation running for the object the are on.
>>>
>>>if we put all the validation on the save, they don't find out about incorrect entries until they try to save.
>>
>>is that a problem? that's what we do and it seems to work fine.
>>
>>>
>>>is there anyway we can keep the valids on the objects yet not have them run if the user hits cancel.
>
>yeah, our analysts want to get the validation message when the actual field is entered and not when they go to save

Hi Gary,

Here is one compromise that has worked for us in the past. Put your validation in the object, but allow blank to be a valid state. Then in the screen validation check to ensure the fields that you validated are not blank. This way when the user enters the data it is validated immediately but if they want to leave the screen, they can just blank the field they are in and got to the cancel button.
This technique has the other advantage of the user being able to enter data into a form in a non standard order without resorting to the mouse. They can tab through fields that they wish to fill in later even if there exists validation and go to any field to start doing data entry.

Darrel