Required

Excellent Alex. Thank you.

Just remember what I say in the video, "no data is better than bad data." If your users forget to put something in, you can always make a query and display all the people who are missing, for example, an address. But if you force them to type something in, you might get bogus addresses, so be careful using the required property.

Thanks for the reminder, Richard. Fortunately, all I am looking for here is a reminder about just one field required by another. If the first field is populated, then the second field must have an input other than 0 before the record is saved. The record is already in edit mode when the user selects it with a button. Combo boxes or list boxes cover all the other fields with critical information for consistency.  Of course, nothing stops anyone from making the wrong selection, but that is easily caught since the entries are restricted. If there is a better way to accomplish the required entry other than using required, I am open to suggestions.

If it involves multiple fields, you may want to consider Table-Level Validation.