Hi all,
I'm trying to implement field validation in a set of tables within a VFP database, using screens generated with the Form Wizard. The edit condition is "not isnull(field)". I have entered a custom error message of "(field) may not be blank". VFP is inconsistent in capturing the null condition, and I can't get it to display my custom error message correctly:

On one table it will only display "failed to update record. Field rule violated."

On the other it erroneously displays my custom error message when the "Add" command button is pressed, instead of waiting for the "Save" button. Then that error message is followed by one or more method-level VFP error messages in a messagebox-type display.

I see that there is a rich history in the UT database on this and related topics. Is there something I can do to salvage the approach I've already taken, since it has already been costly in debugging time.
TIA
Howie Brown