Can you tell me the best practice for this scenario? We want to provide a menu item, that when the user chooses it, will provide job information. The user will enter various prompts such as selected business units, deptids, empl_status, and so on. The result should be similar to query results on the screen, with an option to download.

I could do this strictly with PS Query, but I cannot figure out how to get the complexity I need. For example, there are a few core tables - Job, Compensation, Names, and many tables joined with left outer joins - Address, Email, Phone, and a bunch of code tables to get descriptions. Moreover, we have some criteria for the jobs to choose by date that are not so straightforward.

I wrote this as a regular DB View, but doing it this way doesn't let me provide prompts to narrow down the results.

It looks to me like a Dynamic View might do what I want, but I'm not sure how to fit it in. Since the Query Viewer has the structure I want, it would be nice to embed this DV into a Query, but it does not show up on the available Records to build into a Query.

Any direction would be appreciated. It seems to me this must be a common scenario, so I hope there are ideas out there.