What does your form's Record Source look like? Is it based off a table or a query?

It's from a table, in the table the field is set as Sort Text. this is in my Query:

Like "*" & [Forms]![SearchF]![Post] & "*"

Is your query just a SELECT query or an APPEND query? An APPEND query adds records to a table, a SELECT query should just view current records.

It's not an append Query. My other Queries in the SearchF work just fine. Customer, Phone and State. Just the Post Query is giving me fits. I named it Post, because that is the original name in the original data file.

Troubleshooter: https://599cd.com/Trouble

Try running through some of these solutions and let me know if any of them worked.

Post a screenshot of your Query in Design View.
It sounds like a Join Type issue.

This is it....
But I think I may have fixed it by re-creating the query.

If the first time you ran it you got 9 million records and the table only has about 50,000, then something is definitely multiplying your rows.

That usually happens when the query is joined to another table incorrectly, or when the same table is in the query more than once without a proper join between them. When that happens, Access returns every record from one table matched with every record from the other table. That is called a Cartesian product.

I have seen this happen when someone accidentally drops the same table into the query twice and does not notice because one copy is off screen. The result set explodes in size exactly like what you are describing.

A Cartesian product returns RecordCountA times RecordCountB, so even modest tables can balloon into millions of rows very quickly.

I would open the query in Design View and make sure each table appears only once unless you intentionally need it twice, and confirm that every table is properly joined. That would explain the massive record count.

I rebuilt the Query, it seems to be fine now.
I wish I could show just how had the original Database was messed up. I think I have mentioned this before. NO set standards for
entering phone numbers in particular. sometimes it's like this: 000-0000 or 0000000 or (000-000-0000) or (000)000-0000.
I am certain you would NOT approve of the way it is now. It the database my company uses from a Parts Management Software provider. I just want to know how to make one for myself, so I tore it apart using an Excel Spreadsheet.

I meant how bad....

Richard, the database I am speaking of is an SQL database. It has an Export Dataset Feature in an Excel format. I then Import it into Access, were I then attempt to fix it. Their naming conventions are off compared to yours, but I make it work in Access. For example, the "Post" name is on them. I don't know why they didn't just use PostalCode or ZipCode but oh well. This is the database where is takes 11 steps just to print a Barcode for heaven sake. I just wanted the core of their database so I can play around with it in Access.