Report to PDF using in-memory driver

[Thys]

Hi,

The example app web13 is pretty simple and shows how easy it is to generate a Clarion report to PDF (given that you have the built-in PDF generator) and display it on a web page of its own. But I find that when I try to do the same, the Clarion report procedure executes as expected and actually returns correctly. Seems like the PDF generator then runs on another thread that should show the progress box and then produce the PDF file to be displayed. But in my case the PDF generator runs indefinitely without showing the progress box or ever completing.

I use the in-memory driver to report on - I pre-load the record to print. This is the only difference I found from the example which runs on a TPS file. Any ideas?

Thys

[Bruce]

The file driver won't make any difference.

But if you're using a Clarion Report procedure, then I think your analysis of the PDF Converter running on another thread is inaccurate.
Perhaps your report has no data?

cheers
Bruce

[Thys]

Bruce,

When the report is run, the browser "hangs" awaiting reply from the server. When I then close the server exe with the Close button, the process is not stopped in memory - telling me there is some thread that's still active. Hence my deduction that the PDF reporting runs on another thread.

Regarding the number of records, I do make sure that there is one record added in code (before the report is executed). And even if there are no records, the no-records procedure would have been called (which is not).

Thys

[Bruce]

Hi Thys,

The WebHandler thread runs the report (on the same thread) which in turn runs the converter (on the same thread).

Stopping the WebServer would leave that thread behind, so that's consistent with what you're seeing.

cheers
Bruce

[Thys]

Bruce,

It seems like the IMDD has got a problem in general with reports. I created a simple app (not NetTalk) with a report procedure. The progress window comes up, goes away (after "printing") and then hangs.

Thys