@Chris First, in my opinion, that is the kind of form that's used best for searching, not entry. Rarely do I find that all the fields I need to enter for a record fit in one line of a continuous form.  Add just acquire date, sold date, engine size and engine serial number and see what that does to your form.

You may want to see Richard's Search Seminar (he tackles your question many times there):
https://599cd.com/blog/display-article.asp?ID=2145

My aesthetic is to create a robust form that users first view, like a vehicle form, that shows all the information for a particular vehicle. That way the user can see where they are (sometimes menu descriptions aren't clear enough). Then I add a Search command button to let them focus in on a record if needed.

If you would like to see all of this in action, check out video: 2003 - User, User Group, assigning Users to User Groups
https://www.youtube.com/@adbs_ads

It will give you good ideas for when your db grows to include maintenance logs, accident logs, driver use, etc.

For code cleanness, take the ":" off the Else and move the code down one line, or put it all on one line.

As to your question, you don't want to put it in a global. If you use a piece of code three or more times, then you can add it to a Private subroutine in the same form module. That way you can call it in all the procedures that may use it, including Undo.

As Richard has pointed out in many videos, much better information can be gained from the db if you don't use Active checkboxes for a record, rather an inactive date. Null means active, any date means inactive.

Good luck!

Since the first message was getting a bit long, you may also want to consider using your vehicle table more like a real database and less like a spreadsheet. I would take the make and model fields and make them their own proper tables, and place an ID to those in the Vehicle table. Sorry if I'm assuming you're going to use your db for more than just a notepad.

@Thomas, This is a continuous form where I can double click on a line and open the vehicle form, which contains a sub-form, to enter more detail information.  

I will take a look at the video links you suggested.

Right now I only need a small amount of information on the vehicles.  I have thought about the other items you mentioned and can possibly add them in the future.  

As for as the colon ":", I did not put that in the code, Access must have added it.  

Maybe I've missed something in Richard's videos, but he uses a lot of "IsActive" fields in his tables.  I can see where the date maybe helpful, but right now in my situation I don't really need the date.  

I want to have this feature in one or two other lists.  I don't mind copying or re-writing the code, but I'm trying to learn how to use the global module feature.  

Thanks for your thoughts.

Add this to a Global Module:

Public Sub ShowActive(frm As Form)

    If frm.Controls("IsActiveFilter") Then
        frm.Filter = "IsActive=True"
        frm.FilterOn = True
    Else
        frm.Filter = ""
        frm.Filter = False
    End If

End Sub

Then in the Load event of the Form and the After Update event of your filter Check Box simply say:
    ShowActive Me

Note: change the field names to match the names in your database.
Make sure they are named the same in each Table and on each Form they are needed.

I should also mention if you want to set the Filter Check Box to True when the Form opens you can set its Default Value in the Property Sheet.

@Chris It wasn't clear about your form, if it was just entry or a "search" form. Using a global module is the same animal as a private in a form. It comes in handy to use global either in the form module or some kind of helper module. I tend to use a module to store procedures that can be used by more than one form or in queries as functions.

Kevin shows the code. My approaches (form and shared module) are shown in my "Simple Timer form with module procedures you can call from your own VBA code" in more detail on YouTube, look out at 3:40.

@Kevin, thanks!  I will try that when I get a chance.

@kevin. The code works beautifully. Thanks so much!  I had some trouble at first, but once I typed it correctly it works like magic.