Tom, This may be one of those issues that can only be traced down by creating a sample for RBTI. Personally I have not noticed any issues printing compiled vs uncompiled. But I haven't had a chance to install the latest update on 12/12.
Jan -----Original Message----- From: Tom Frederick <[email protected]> To: [email protected] (RBASE-L Mailing List) Date: Tue, 13 Dec 2011 09:36:45 -0600 Subject: [RBASE-L] - Printing: compiled vs. uncompiled I am having problems getting print programs that work in uncompiled v9.1 64 to also work in compiled v9.1. Latest updates applied. Basic process: create the report, bring it up in a PDF viewer, decide to keep it or erase, if erase delete, if keep store it on the network, and update table with info needed to retrieve it. For a long time each print command had its own set of commands in a BIT BUTTON. Most of the print command process is identical so I created a list of variables adjusted for each report and stored the actual print process in a table. This line runs the entire process: RUN SELECT CmdCode FROM RMD_FILES WHERE CmdName = 'PDF_Reports' This works great in the uncompiled version and prints every time regardless of size or number of variables involved. In the compiled version, small 2-3 page reports pop right out, but big complicated reports (6+ pages, lots of variables) get stuck and never finish. Immediately run the exact same database in uncompiled form and out comes the big report like always. If I go back to the original setup of each print command having everything in one place, the compiled version then works correctly. I really like the RUN SELECT option because there is only one set of commands to adjust compared to many print buttons. Is there some adjustment I need to make for the complied version? Tom Frederick President/CEO Elm City Center 1314 W Walnut Jacksonville, IL 62650 W- 217-245-9504 F - 217-245-2350 E - [email protected]
