Long reports timing out

[terryd]

I use the standard Clarion pdf report generator.
If the report takes a longer than normal time I get a message that the server has disconnected.
I use p_web.Noop() in the take next record embed and this seems to keep the connection alive, but when it comes to the 'creating page n of n' message after a number of pages I get the timeout. AFAIK there is nowhere to place the p_web.NoOp() method while the pdf is being created. Am I correct? I hope not.
Another query
I use Clarion source code templates to do various operations e.g. totalling values etc. Because this is Clarion source code and not netweb source code I can't use p_web.noop() in the source code. Is there another way to keep the connection alive while the source code is processing. I know that the code continues processing even though there is no connection but there is no way to tell the user that he should wait once he has been disconnected. He can reconnect immediately and he will hang if he tries to do the same operation again because he thought it failed.

[Bruce]

Hi Terry,

Any operation that takes longer than 30 seconds is likely to time out the browser. So, as you noted, calls to p_web.Noop() are a good idea.

Yes, there may be places, where you can't add that code - although scratching around for an embed point sometimes helps. If all else fails then you need to adopt a different approach - for example generating a intermediate web page, or emailing the report to the user etc.

There's no other way to keep the connection alive, so I recommend adding embed points to your code templates, and then using the optional parameter approach to pass p_web to those procedures.

cheers
Bruce