Took a look at db. What you say doesn't work could be as simple as
Code:
SELECT VendorT.VendorID, VendorT.[Company Name], UniqStateT.State, POCT.FirstName, POCT.LastName
FROM (VendorT INNER JOIN UniqStateT ON VendorT.State = UniqStateT.State)
INNER JOIN POCT ON VendorT.VendorID = POCT.VendorID
WHERE (((UniqStateT.State)="ga") AND ((POCT.LastName) Like "*miller*"));
and having an unbound control for searching on either first or last name. However I see that the focus is on modifying filter in vba rather than record source of form or using queries as filter objects. Regardless, you have no controls for a name search.
but you do have some design issues, I think:
-some fields contain mixed data (numbers and text)
-tables that look like lookup tables are indexed but allow dupes (e.g why would you allow duplicate state abbreviations?)
-there are few PK fields but what's odd is that in relationships, POCT.POCID shows it's a PK but not in design view of table. Can't recall ever seeing that before
-no referential integrity is set anywhere, so if you change a value for Specialty it won't propagate. If you used a different PK rather than using values as PK's (e.g. autonumber like 1 instead of "Canopy") then you wouldn't need to, but because you don't, you need to.
-you cannot search on company??
-if I enter 4 search parameters while drilling down and 1 of them needs to change, you have no way to negate just one and the entire search needs to start over. That's not a design flaw but it is a user-friendly type of thing. A blank as 1st combo value could help.
I was going to point you at AB search form but see that I already did that. A thorough study of it should solve your problems - if you have table designs that can support it.