<hr>I usually avoid using a tab control because of the performance hit, but the query only deals with the current parent record, so it seems to work. <hr>Actually the native Access tab control imposes very little performance penalty - performance penalties from subforms typically outweigh them significantly. We often use multiple embedded tabs for complex forms - it makes them much simpler and easier to understand what you are seeing. I presume by using filters you mean what you can do with a right-click from the UI - in cases where we want that and have totals or expressions, we build the entire query for the subform on the fly in code, and change the Data Source for the subform. But it can lead to lots of complicated code. An alternative when you can reasonably predict what kind of view the user wants, you can use a drop-down combo to set either the filter or the data source.