Can you post some screen shots so we can see what you're getting?

Richard, I really appreciate your help.  I am trying to get the catalog complete and all parts on shelves ASAP.
If you need anything further, or, if you do not have time please point me in the right direction.
Wayne

Wayne,

The criteria looks good. Try dynamically changing the RecordSource of the form in the AfterUpdate event for the search box.

Private Sub PartNumberSearch_AfterUpdate()

    If IsNull(PartNumberSearch) Or (PartNumberSearch) = "" Then
        Me.RecordSource = "SparePartT"
    Else
        Me.RecordSource = "PartNumberSearchQ"
    End If
    
End Sub

Since you said you can't even click in the search box, double check the properties for the form as well as the search box.

Make sure the Allow Edits, Allow Additions are set to yes.  For the field itself make sure that Enabled is set to Yes and Locked is set to No

Well Scott you got me half way there.  Thank you very much.  The query still has a issue.  I put the = sign in the criteria.
=[Forms]![PartListF]![PartNumberSearch]

But when I save and close, then reopen in design the = is gone.     [Forms]![PartListF]![PartNumberSearch]

If I do not close the query.  the = sign remains and the search works.

First of all - Are you getting any errors?  If so what are they.

Second - Try designing the query but instead hard code one of your parts into the criteria line.
Then open your form and make sure it works ok.
So using your picture above ="885"  should bring up Cotter Pin.

If that works let's rule out as much as possible.  Go to the Troubleshooter
I would start out buy running down the list up to and including the reboot.  I don't think a reinstall is called for.

Let us know what your results are.

Scott
Many thanks.  Everything seems to be working well now.

Wayne you're welcome.
What ended up being the issue?

Your suggest to check Edits and Additions proved fruitful.
However, the missing = sign turned out to be a nonissue.  I discovered that Access removes the sign as a default.  I noticed that it was happening in Rick's Tech Help and his expressions worked fine.
I guess we'll chalk this up to NEWB error.
Thanks again.