New Post: PDF reports in SQL server (client server) environment

Hi Claudfox,

This is just beautiful. First I have to comment on your excellent work in making this system so stable and easy to use.

I have almost finished with my PDF module and would like to share my experience for anyone who may be thinking of going ‘mobile’ with this product.

Just a couple of points

1. My requirement was to create PDF reports from multiple related tables. Since C/S does not have a DBC file, I had to create a empty DBC file to be shared by all web users. When the reports are created, I load the required dbf tables into this DBC and immediately unload and destroy them, once the PDF file is created.
   

I could not re-set pdfrun.print2pdf data session (when running it from IIS) therefore I was required to open and then relate multiple tables from within the oPDF object itself. This I did by changing the following line in MakePS()

&lcRecordSelect

To ..

EXECSCRIPT(lcRecordSelect)
This allowed me to inject multiple line commands into this exe.

1. I also had to send a couple of variables into this report. I could not figure out how best to do that so I sent them as ‘public’ into the lcRecordSelect. I haven’t tried creating them as properties in oPDF object and poping them as private from within the MakePS()
   

Am I on the right track? Is there a better way to achieve this? I've never created public variables before.


An observation: However, it may be local to my system ....

oResponse.Redirect(lcNewPath) && redirect browser to created file
oPDF = .NULL.
release oPDF

needs to be...

oPDF = .NULL.
release oPDF
oResponse.Redirect(lcNewPath) && redirect browser to created file

Othewise, oPDF keeps its hold on all files and eating memory.