If you set the field to Required in the table, then you don't have to change all the forms.

I did exactly that; however, the form continues onto the next field. When a click on the "Save" Button: (DoCmd.Save, DoCmd.Close); it does not give you an error for the missing required fields!  Then upon opening the corresponding table, that record isn't listed in the table.   Never received any type of error from Access.   I went into the Options and turned on all three settings under Confirm.  Closed and reopened the database and tried again; still receiving no error message, and no no new record added to underlying table.  I'm using Office 2019 Professional Pro edition.

William when you change mid-stream the existing records don't get updated.  You should have to update them manually.
If you enter a new record then the required will kick in.
Is that what is happening to you?

No; I've completely closed the database base, selected the form which adds a new record and intentionally skipped the required fields.  If I use the Button that I created, no error message or new record saved into table.

Upon further testing, if I close the form using the right mouse click options, then I do receive an error message on the required field.  After confirmation of  the Access error, another Access message pops up (Yes/No) and states that the record can't be saved at this time.

In my research, I located another content provider who created a macro that provides a "readable" error message and then returns the cursor (DoCmd.GoToControl "FieldName") to the required FieldName.  The cursor will not move away until a value is entered into that field name.  That's when I came up with the idea of a VBA module (passing the FieldName as a variable) so it can be in multiple fields and forms.

Also, how do I access the Code Vault?  I haven't figured out the navigation to it.

Two spots for Code Vault  Up top  Combo Box next to Order.  Down at the bottom in the Info Section.

I'll have to take a look and see what I can find.  I tend to not set required because as Richard says "no data is better than Bad data".  I much prefer validating the fields that I really need to have in the save button events.

Yeah, I very rarely use the Required field unless it's something like a required foreign key.

Thanks for the input...