Normally when two tables are joined, rows are excluded that don't meet the join criteria. However, in this query I'm working on, the table on the left side of the join only has one row and one column, whose value references a form field. In this case, every row of the table on the right side of the join is returned, even though most of them don't meet the join criteria. (This defeats the goal, which is to filter the rows in the right-hand table based on the join.)
Is this a known bug/limitation? Is there a work-around?
You might wonder why I'm going about it this way instead of using VBA in the form, and the short answer is that I'm trying to save time/work. Since I already have a query that runs a bunch of tests and shows statistics based on values in another table by doing a left join to it, I don't want to create a new method to run the same tests on values that the user can provide, which would require me to start maintaining all of those test criteria in two separate places.
If more detail is needed, I can provide instructions for recreating the behavior I have described.
Is this a known bug/limitation? Is there a work-around?
You might wonder why I'm going about it this way instead of using VBA in the form, and the short answer is that I'm trying to save time/work. Since I already have a query that runs a bunch of tests and shows statistics based on values in another table by doing a left join to it, I don't want to create a new method to run the same tests on values that the user can provide, which would require me to start maintaining all of those test criteria in two separate places.
If more detail is needed, I can provide instructions for recreating the behavior I have described.