We have an 81 line compound report generated by 81 focexecs. Sometimes the report runs all the way through, and sometimes it stops halfway. If we wait long enough we get a message that says, " No Query Data to Decode" and the part of the report that was displayed goes away. A view source of one of the partial report results usually shows only part of the &ECHO... (ie. the report goes to line 75 but the ECHO stops at fex 64..etc.)

In addition we have a report that runs fine when the reclimit is set to 10k, but when the reclimit is set to 50k the report gets a page not displayed error when running EXL2K, and when running HTML it never returns but uses over 2GB of virtual memory on the desktop paging file.

Are there any server settings or client side settings that can be changed to help solve this issue? It almost appears as if there is not enough memory on the client side to process.

Hi gw2006,

Has this issue been resolved on your side?

I ran some search on Information Builders' online documents and came to the understanding that this issue should be reported to Information Builders' Customer Support Services for further debugging. The phone number is 1-800-736-6130, or you may access the online system InfoResponse at http://techsupport.ibi.com. Here is a list of information to be ready when you call: http://techsupport.ibi.com/before_you_call.jsp.

Hope this helps.

Cheers,

Kerry

We actually are using a workaround. We are going to chunk out the reports into smaller groups. Not what we wanted to do but unfortunately we currently didn't have the time to continue to research.

Thanks for the assistance.