Using the sample Customers database, I can advance to a new record in extended mode (Update Mode), enter data in an element, then tab out. I can then go back to that element and delete the entry, press F10, and save a blank record. To prevent this, calling NotifyForm(1) isn't a solution, because then I can't retreat (F9) to the last saved record in the Result Set. Is there a way I can prevent saving a blank record, yet still retreat to a previous record?

Ok. I see what is happening and it is somewhat limited to Customers.db. The check box "Active" element is defaulting to a "NULL" state if the record has never been viewed. But, once viewed it gets initialized - and the engine believes that that is a change of value, so the record is not blank.

Once I deleted the check box element, retreating from a changed but now all blank record, works as it should: retreats but does not commit.

So - basically, this bug seems be limited to forms with check boxes. Though, there may be other element types (not on the Customers form) that exhibit similar behavior.

Yah. I'll look into checkboxes to see what makes them so special.

Very cool. Thanks Mark.