I don't find modifying the stored procedures to be a hassle, myself.
Even were I to be using RUN SELECT, I would test the file outside the
database before making a permanent modification in any event, so
unloading the stored procedure and modifying it using RBEDIT is not any
different to me. Different strokes for different folks, I think.
Albert
On 5/29/2015 10:53 AM, Javier Valencia wrote:
Albert,
I find the RUN SELECT approach to be easier to understand and to
maintain, maybe in part because I really don’t use stored procedures
that much since I started using RUN SELECT. When you store the code in
a column, you can go to it and edit it as needed and also makes it
very easy for me to upgrade client‘s databases with very simple code.
You can always restrict access to the table so users do not modify the
code.
Javier,
Javier Valencia, PE
O: 913-829-0888
H: 913-397-9605
C: 913-915-3137
*From:*[email protected] [mailto:[email protected]] *On Behalf Of
*Albert Berry
*Sent:* Friday, May 29, 2015 11:25 AM
*To:* RBASE-L Mailing List
*Subject:* [RBASE-L] - Re: Forms: Custon Form Action
I use stored procedures a lot, but have never even tried RUN SELECT a
command file. I wonder what the advantage is of one over the other.
Albert
On 5/28/2015 1:56 PM, James Bentley wrote:
Thanks to all who offered suggestions. I had one other thought and
that is to store the code in a STORED_PROCEDURE
then a simple CALL procedurename () would execute the code. I do
have a table where I store code for execution.
Jim Bentley,
American Celiac Society
1-504-737-3293
------------------------------------------------------------------------
*From:*A. Razzak Memon <[email protected]> <mailto:[email protected]>
*To:* RBASE-L Mailing List <[email protected]>
<mailto:[email protected]>
*Sent:* Thursday, May 28, 2015 11:27 AM
*Subject:* [RBASE-L] - Re: Forms: Custon Form Action
At 12:15 PM 5/28/2015, James Bentley wrote:
>Within a form you can define eeps for the following events:
> * On Before Start EEP
> * On After Start EEP
> * On Before Design Action
> * On Close Designer Action
>
>my question is if I have defined a Custom Form Action
>Say "DefFormVariables"
>
>Are there restrictions on when I can use
> PROPERTY RBASE_FORM_ACTION DefFormVariables ' '
>
>I have several forms that require extensive
>SET VARIABLE statements.
>
>I would like to consolidate them into a Form Custom Action
>and call them in then above mentioned EEPs. I can not find
>in the Help Documentation a mention of restrictions on using a
>PROPERTY RBASE_FORM_ACTION command.
>
>Any help would be appreciated.
James,
Technically, all Custom Form Actions, if defined, are accessible
right after the form is completely drawn/loaded. Thus, the first
opportunity to use/execute the Custom Form Action would be the
"On After Start" and anywhere after that.
Hope that helps!
Very Best R:egards,
Razzak.
www.rbase.com <http://www.rbase.com>
www.rbaseX.com <http://www.rbaseX.com>
www.facebook.com/rbase <http://www.facebook.com/rbase>
--
32 years of continuous innovation!
17 Years of R:BASE Technologies, Inc. making R:BASE what it is today!
--
--
A democracy ..." can only exist until the majority discovers it can vote itself
largess out of the public treasury."
Attributed to Alexander Fraser Tytler 1747-1813
--
A democracy ..." can only exist until the majority discovers it can vote itself
largess out of the public treasury."
Attributed to Alexander Fraser Tytler 1747-1813
