----- Original Message -----
From: "Jan Barley" <[EMAIL PROTECTED]>
To: "RBASE-L Mailing List" <[email protected]>
Sent: Monday, September 29, 2008 11:26 AM
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.
A.1. Code that is incorporated into the form is run from memory, not loaded
from diskfile as the "Old Tech" of the compiled files.
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!
A. 2. If you have a routine that gets called from multiple locations you
can do either of two approaches. Stored procedure is one and "Run Select" is
the other. If it is something that returns a value or calculation, Store
Procedure would be favored. If it is simply a procedure, then I would favor
the "Run Select". If you are not familiar with "Run Select", It is simply
placing your code in a VarChar data format in a table, giving the row of data
another column for the name of the routine (essentially the same as the old
$Command where the next line was the name of the routine) and then call the
routine like:
Run Select SomeVarCharDate from SomeTable where RoutineName =
'TheNameOfTheRoutine'
That's all there is to it.
I appreciate y'alls thoughts on this.
Jan Barley
