Thanks Craig... I'll give that a try.. I think I am going to move it to the SAVE button on the ADD/EDIT toolbar. Then just RETURN it back with a SETFOCUS to a field to correct. But this brings up another interesting point... when is a field NULL vs BLANK (or 0)?



>>I want to check to make sure a field or two have at least something in them before a record is saved. I was going to use the VALID method for the field with....
>>
>>IF ISBLANK(THIS.VALUE) or ISNULL(THIS.VALUE)
>> MESSAGEBOX("Cannot be left blank",16,"ERROR")
>> RETURN 0
>>ENDIF
>>
>>This will work fine except.... when I pick the REVERT button in my DB toolbar class... I need to skip this routine. Is there a way to do this? I thought if I knew WHAT was clicked, I can check for the REVERT button and then in the VALID routine, ignore the checking steps.
>>
>>Suggestions?
>
>Set the Cancel property to .T. on the revert button then:
>
>IF LASTKEY() != 27
> * Do the validaiton
>ENDIF