Is there a widely accepted conventional method for passing user input from a form to control the printing of a report.

Suppose I have a simple form that allows the user to select customer name, one of two sort orders, one of two filter options and a 'preview prior to printing' option. Being a procedural programming dinosaur, it seems like one would run the form then call the report generator with some parameters. Of course, as far as I can tell, you cannot pass parameters to a report (I am new at this, so maybe you can). I am loath to use public or private variables.

What I've come up with (and don't even know if it'll work yet) is having the form perform a query based on user input then call the report generator which accesses additional form properties with a 'thisform' reference. Just on general principles, this seems bassakwards ... it seems like the variable input needed by the report generator should be encapsulated in the report definition ... not in the object that invoked it. But I'm new to this OOP paradigm so maybe that's how it's done these days.

Didn't find this question in the FAQ's so here I am. Any edification would be greatly appreciated.