Run select CmdCode from CodeLibrary where cmdname(or number) = 'postorder' (or 6)
This works great, and I believe it was Mike B who got me started doing this. I added some columns for update and change information. R>lis codelibrary Table: CodeLibrary No Lock(s) Descr: Command Files - Run select No. Column Name Attributes --- ------------------ ------------------------------------------------------ 1 CmdNum Type : INTEGER AUTONUMBER 2 CmdCode Type : LONG VARCHAR 3 Form_or_Menu Type : TEXT 40 4 Cmd_Desc Type : TEXT 40 5 Cmd_MiscInfo Type : LONG VARCHAR Current number of rows: 211 Kenny From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Jan Barley Sent: Monday, September 29, 2008 10:27 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Application Design Questions Hello all! I am in the process of doing a complete overhaul of my 6.5 applications. I have some design questions and I would appreciate any and all input! 1. I know its old school thinking to put routines in compiled application files and the current strategy is to incorporate them into forms and reports instead. Is there a big performance difference in calling to an application vs. within the form? I know its old school, but I am still a little leary of relying on passwords to protect my programming. 2. Say I go out of my comfort zone and write the applicaitons within a form/report. Is there any way to call a procedure from another form/report? In the old way, I would name a procedure in a compiled application, then call it from wherever I needed it to run. I just hate to repeat code if not necessary, especially if I have to change it at some point! I appreciate y'alls thoughts on this. Jan Barley
