>> What do other people use to ensure a control is not left blank once it has
>> focus?
>>
>> Michael G. Emmons
>
>In these Windows days I do not think it is acceptable to have the use
>'traped' in a field and not let him leave it blank, even if at save time
>it is required. What I do is to clone the table and use the clone's
>fields as controlsources, write valid clauses that will prevent the user
>to enter invalid values for a field, but always allow to leave if the
>field is blank.
>
>At save time, I check only the required field fors 'blankness', and deny
>permission to save if rules are transgressed. Some of these rules I
>enforce through the DBC triggers.
>
>Voilà. You're the one who asked :).
>
>Marc

I agree that the fields should be checked at save time. I do this. But, I just wanted to make sure that once the user is there he has to go ahead and enter the information. It saves time since the user won't have to go back to this particular field once he tries to save the record.
They would have to enter the data anyway, so why not make them do it when they are there?