That's completely up to you. I wouldn't. If they're adding a new record, push it for them. However, I have had clients complain about accidental new records being added all the time... so it's completely up to you how you put your Legos together.

In my old job I had an "Add New" button (see picture below) -- in addition to all the buttons mentioned in Richard's video: Edit, Save, Cancel, etc.

Also consider using an unbound form for data entry, where all controls on the form (and the form itself) are unbound, and any changes made to the data have to be done with VBA code.  And you don't have to worry about a user locking up a table, because no table is bound to anything.

Making an unbound form is a tall task, since everything has to be done with programming: retrieving data from tables, displaying data, saving, etc.  But if your tables are mission-critical, consider that; it might be worth it.  I did that in my old job.  The forms in my pictures below are all unbound.

If you foresee yourself developing a web interface for data entry in the future, you also need to know how to work with unbound controls, because everything is (often) "unbound" on the web.

Using VBA Recordsets, how can you detect that you're currently in the New Record position in the Table?

If you want to add a new record in a situation like Kevin suggests with an unbound form, you'll just set the ID to something like 0, and that way when you save the record, your code will know to add it. There's many ways to do it. That's how I would. You could also set a variable like "IsNew" or something. I actually show how to do this exact example in Access Developer 18, which I see you have, Gary. Lesson 4.