I've an application that shows a Simple Table with 48 columns and ~50K rows after filter and users need download this data. When I click in the XL icon, the server generates a 55MB XLS file in the QvPrint folder (it takes about 5 minutes) but the client (AJAX or Desktop) remains waiting (with the sand clock mouse pointer).
I modified the QvsTimeout in QvWebServer's config.xml (current value: 600 = 10 minutes). Also, seted up "Maximum inactive session time" to 2000 s (33 min). Before these changes I got "Socket closed by client" in the Sessions log, but now I'm getting "Session expired after idle time".
Does the entire table need to be exported in one go? You could have 24 fields in one table and the other 24 in another and the users downlaods it in two files?
Other than that you may be looking to rationlise such a large amount of data by more aggresive filtering.
QV9 also has the function to export entire tables to csv in the load script (assuming you are not perfomign complex calculatiosn in your chart) and tied in with sectional reduction you could actually have the application automatically populate shared folder with csv's of the needed data pre-filtered at specified times without any user interaction.
Even i am facing the same issue at my end . when i export the file in IE it works fine and when i export the small file in ajax then also works fine but it wont work when no of rows are more than 65K. . is this a limitation in ajax or something else . can anybody suggest me on this