A family of Microsoft relational database management systems designed for ease of use.
First, this is one of the reasons why we recommend that you don't use lookup fields on the table level. They mask what is actually stored in the table. I would recommend that you remove all the lookup fields by changing them back to text boxes. Do all your lookups on your forms using list controls.
Second, This is one of the reasons I rarely use parameter queries. They are very inflexible. Query criteria should be entered on forms In your queries you can use:
=Forms!formname!controlname
to reference the value in the control that you want to use as criteria. In this way you can have the user select from a value rather than enter a value that might not match.
So for example (it would have been better if you used real examples rather than field A, etc.) lets say you have are tracking sales in stores. And you want to show the sales for a specific store. So your Sales table looks like this:
SalesID (PK)
StoreID (FK)
SaleDate
SaleAmont
So what is stored in this table is a StoreID taken from your Stores table which would look like:
StoreID (PK)
StoreName
StoreAddress
etc.
Because of the lookup field you see the StoreName not the StoreID which is what is actually stored. So if the user enters the Storename as the criteria its not going to match. But if you use a combobox with the same Rowsource, you will be comparing the StoreID.