I tried to use the RUN SELECT for everything I could in my application. However, I have found there sometimes is a limit to how a program will operate using the run select. In some cases I have had to do use another method to run the command. Where the RUN SELECT had problems with executing, the following is general process I have used to replace the RUN SELECT and have had no problems in running the command.
Select command into variable from commandfile where commandid = idnumber Output command.rmd Write variable Output screen Erase variable Run command.rmd Erase command.rmd This requires a few more steps, but it still allows me to keep most of my code in the program. Gary From: [email protected] [mailto:[email protected]] On Behalf Of Tom Frederick Sent: Wednesday, December 14, 2011 11:39 AM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: Printing: compiled vs. uncompiled Paul and Jan, Everything is recompiled with the 12/12 update. So I put the text of the PDF command code back into the BIT BUTTONs that create the biggest reports. Make no changes to any other print BIT ... and the compiled programs work correctly regardless of which print BIT BUTTON is hit. Haven't got a clue what is different except no RUN SELECT for two buttons. I did notice I had several reports where the sub reports lost the slave tables they used. That was easy to fix, but I will be watching those to find a cause. Appreciate your ideas. Tom Frederick President/CEO Elm City Center 1314 W Walnut Jacksonville, IL 62650 W- 217-245-9504 F - 217-245-2350 E - [email protected] From: [email protected] [mailto:[email protected]] On Behalf Of Paul Buckley Sent: Tuesday, December 13, 2011 10:07 AM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: Printing: compiled vs. uncompiled Tom, This may be a silly question but did you update the compiler and re-compile the application? Just thinking, Paul From: [email protected] [mailto:[email protected]] On Behalf Of Tom Frederick Sent: Tuesday, December 13, 2011 10:37 AM To: RBASE-L Mailing List 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]
