cloaked wrote:A process of this nature might work better using an export: XML or export: CSV report template, which won't go anywhere near pagination. When a page containing a report using these templates is requested APEX sends the report results in XML or CSV format rather than rendering the page. This should be faster, avoid complications with pagination, and be easier to parse in Excel.
Thanks for the response. Yup, you're correct. Downloading to a CSV might be better. I've set reports up that way many, many times. I have even developed pages that import from a CSV into APEX using PL/SQL, years before it was an APEX feature. I initially set the report up to allow it to be downloaded, but the user doesn't want it to work that way.
The worksheet will be used by a lot of people in our accounting department and they want the process to be as simple as possible. Right now Excel opens up the APEX page, logs into the application, passes parameters to it for the month and company, hits the Select button, waits on the report to build, then automatically imports it, and finally closes the page. It is quite slick. Yes, it takes 5 minutes to run, but the user is OK with that given what the automation provides.
So, in order for the automated import to work properly all 45K rows need to display on one page, without pagination. I currently have pagination on the page simply to determine if APEX is returning all of the rows.
cloaked wrote:Combining the three statements above suggests to me is that the "SQL for the report outside of APEX" isn't exactly what's being run to generate your Apex report. You haven't provided the SQL, so I can't even begin to guess at what might be different. What I would suggest is to run the SQL outside of Apex and get your 46K rows. Copy and paste that exact SQL into Apex. Do not change anything, including referencing your page items. Run the report. If it still only returns 15,500 rows, then something is screwy.
...Using the same WHERE condition, when I run the SQL for the report outside of APEX it returns 46,840 rows.
...When I run the page and enter the selection criteria the report only returns 15,500 rows.
...Also, the pagination suggests that all rows were returned because it reads - row(s) 1 to 15500 of 15500.