I'm using the following code in all my forms to prevent users from creating blank records by transitioning into Add mode from the last record of Search mode:

// Prevents entering Extended Mode from Search-Update

IF @Mode() = 1
THEN
	{
	IF @ResultSetCurrentPosition() = @ResultSetTotal()
	THEN
		{
		NotifyForm(NOTIFY_FORM_EXTEND_DISABLED)
		}
	ELSE
		{
		NotifyForm(NOTIFY_FORM_EXTEND_ENABLED)
		}
	} 

However, one user has found a way to create blank records in my Personnel database, and she doesn't know how she's doing it.  Neither do I, but I'm guessing it has to do with using F10 instead of the "Save", "Save-Continue" and "Save-Exit" buttons I've made.

Is there a way to prevent F10 from saving a blank record if, let's say, the field FullName is blank?

Form -> On Form Entry

Thanks Erica, I will update my code.

On closer examination, I've found that what I thought was a saved blank form is not actually blank.  The value "2,010" exists in the Age field.

This field is calculated on-form-entry by the following code"

// Calculates the employee's age

IF
(
@MODE( ) = 1
and not
	(
	@IsBlank(Birthdate) and
	Age = (@YEAR(@DATE)-@YEAR(BirthDate) - ((@MONTH(@DATE) < @MONTH(BirthDate))
	or (@MONTH(@DATE) = @MONTH(BirthDate) AND @DOM(@DATE) < @DOM(BirthDate))))
	)
)

THEN
	Age = @YEAR(@DATE)-@YEAR(BirthDate) - ((@MONTH(@DATE) < @MONTH(BirthDate))
	or (@MONTH(@DATE) = @MONTH(BirthDate) AND @DOM(@DATE) < @DOM(BirthDate))) 

This is firing off in Search mode even when Birthdate is blank, so I've written in a bug there somewhere.  Not sure if it's my Mode checking, or the nested "and not", or something else.  Help spotting it would be appreciated.