I am unsure of how to pass filter information from the user into the reports. I believe I wanted something similar to an xDialog, which obviously for desktop only, so created a Dialog2 that was not linked to a table and would just capture variables from there. The second part of the question and probably related is that I have written a multitude of different reports that I am unsure of the best practice on running from a Tabbed UI menu. My thoughts were to create an a5w page with buttons placed on it for each report that would have a Dialog2 with an embedded report.
The Dialog2 I created works for capturing the filter data and then is passed though via arguments into the SQL Filter. This is fine if all parts of the Dialog2 are filled out by the user. e.g. The beginning and ending date, job name, employee name, etc. If the user wants to, for instance, have all employees and doesn't fill that field in the Dialog, the SQL statement gets and error because of the null argument. Basically, I need the dialog to work like the search function does in a grid. i.e. The search works regardless if all search criteria are filled in. If I can't figure this out, it appears that I must have a Dialog2 for each and every report and every report filter scenario. e.g. A Dialog2 for when searching on Date only, another Dialog2 when searching on Date and job name, another Dialog2 when searching on job name only........ This obviously is not practical and am sure I am missing something. I am sure there is another way, just don't know how to elegantly feed the filter data from the user to the report.
I looked at the videos and discovered that "Power Search for Embedded Report" does what I need, but I apparently did not get that add-on. I wrote to Alpha to see if that can still be purchased for v11, but haven't heard back. Maybe the Alpha office is closed this week?
Your direction is appreciated.
The Dialog2 I created works for capturing the filter data and then is passed though via arguments into the SQL Filter. This is fine if all parts of the Dialog2 are filled out by the user. e.g. The beginning and ending date, job name, employee name, etc. If the user wants to, for instance, have all employees and doesn't fill that field in the Dialog, the SQL statement gets and error because of the null argument. Basically, I need the dialog to work like the search function does in a grid. i.e. The search works regardless if all search criteria are filled in. If I can't figure this out, it appears that I must have a Dialog2 for each and every report and every report filter scenario. e.g. A Dialog2 for when searching on Date only, another Dialog2 when searching on Date and job name, another Dialog2 when searching on job name only........ This obviously is not practical and am sure I am missing something. I am sure there is another way, just don't know how to elegantly feed the filter data from the user to the report.
I looked at the videos and discovered that "Power Search for Embedded Report" does what I need, but I apparently did not get that add-on. I wrote to Alpha to see if that can still be purchased for v11, but haven't heard back. Maybe the Alpha office is closed this week?
Your direction is appreciated.
Comment