Well, yes, but that would be more time consuming for both of us. I'd have to explain about Public functions and how to use that in a query.
Probably the easiest way would be to just create a seperate table for your input values and link the form to it.
Next, in your query, add that new table to the the query.
If the input values are expected to be exact matches, you can simplify it by linking the input value column to the column in the main table that contains the specifications you're trying to isolate.
If the input values are not exact matches, then do not link the two tables, but rather use the values in the critera section as a greater than, and/or less than, which ever is your preference.
Test that query by manually adding some values to the new table and then look at the query in datasheet view.
When you have it working the way you want, then open your form in design view, and add a sub-form linked to that query.
As support for the form, you'll need to add an extra query to clear the temp table when you're done or you could end up with more than one record in it, which would add unwanted results to the sub form.
The idea is that this new temp table only have one record in it.
If it need to have more than one column (e.g. a high side and a low side), that's cool.
Your form will need to have a button to requery if you change the values, and it will need another button to close the form and then perform whaat ever other functions you want with the record matches.
I don't know what else you've got going on before or after this process.
YOu can build this button functionality in Macro builder, and later, if you get to feeling extra motivated, you can convert the macro to VBA and start reading it to try and understand a bit more about VBA.
Is this getting close for you?
