If I was going to do it, I wouldn't open the query. Instead, I would create a datasheet form based on the query, and then use the OpenForm method where you could pass a filter/criteria in the WhereCondition argument to limit the data displayed.
But there are 175 different arguments to be made? If the boss said I had to make this work as is, I'd select all of those buttons in design view and set their click event to call one function. That function could accept either the button name or caption as an argument, but that would require providing that info for each separate button, either through the function call or tag property. I might try to just use ActiveControl property instead.
However, given free rein, I'd start over with a different form design.
By the way, I agree with tBD's suggestion to filter a form but rather than have 175 Click events (1 for each button) have just one function is what I'm saying. You don't seem to have that form yet. Why not create that and post back - preferably with a db copy?