Albert and Buddy,
STORED PROCEDURE in RBase serve several functions:1. They can be TRIGGERS they
cannot have parameters and run in one of six circumstances for a particular
table Before/After Insert, Before/After Update, Before/After Delete.
Additional Stored Procedure, Run Select .. can be from the appropriate
trigger2. Procedure similar to a ".RMD" or ".EEP" with or without input
parameters and no RETURN value
3. Stored Function with or without input parameters and a RETURN value
Triggers always get executed at the appropriate time for a TABLE record.The
other uses require an appropriate CALL syntax. Jim Bentley, American Celiac
Society 1-504-305-2968
From: Albert <[email protected]>
To: [email protected]
Sent: Tuesday, August 25, 2015 10:27 AM
Subject: [RBASE-L] - RE: RUN SELECT or Stored Procedure?
Thanks, Buddy - I'm still confused, though. A Stored Procedure only runs when
you CALL it. I'm still foggy on the distinction between these two command lines
anywhere in my code:
RUN SELECT CodeBlock FROM CodeBase WHERE CodeBaseName = 'PaymentTotalsUpdate'
AND PKNumber = .vInvNo
CALL PaymentTotalsUpdate (.vInvNo)
Albert
On 2015-08-25 9:21 AM, Buddy Walker wrote:
<!--#yiv9174646187 _filtered #yiv9174646187 {font-family:Helvetica;panose-1:2
11 6 4 2 2 2 2 2 4;} _filtered #yiv9174646187 {font-family:"Cambria
Math";panose-1:2 4 5 3 5 4 6 3 2 4;} _filtered #yiv9174646187
{font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;} _filtered #yiv9174646187
{font-family:Tahoma;panose-1:2 11 6 4 3 5 4 4 2 4;}#yiv9174646187
#yiv9174646187 p.yiv9174646187MsoNormal, #yiv9174646187
li.yiv9174646187MsoNormal, #yiv9174646187 div.yiv9174646187MsoNormal
{margin:0in;margin-bottom:.0001pt;font-size:12.0pt;font-family:"Times New
Roman", serif;color:black;}#yiv9174646187 a:link, #yiv9174646187
span.yiv9174646187MsoHyperlink
{color:blue;text-decoration:underline;}#yiv9174646187 a:visited, #yiv9174646187
span.yiv9174646187MsoHyperlinkFollowed
{color:purple;text-decoration:underline;}#yiv9174646187 p
{margin-right:0in;margin-left:0in;font-size:12.0pt;font-family:"Times New
Roman", serif;color:black;}#yiv9174646187 p.yiv9174646187MsoAcetate,
#yiv9174646187 li.yiv9174646187MsoAcetate, #yiv9174646187
div.yiv9174646187MsoAcetate
{margin:0in;margin-bottom:.0001pt;font-size:8.0pt;font-family:"Tahoma",
sans-serif;color:black;}#yiv9174646187 span.yiv9174646187fcourierfixed
{}#yiv9174646187 span.yiv9174646187BalloonTextChar {font-family:"Tahoma",
sans-serif;}#yiv9174646187 span.yiv9174646187EmailStyle21
{font-family:"Calibri", sans-serif;color:#1F497D;}#yiv9174646187
span.yiv9174646187EmailStyle22 {font-family:"Calibri",
sans-serif;color:#1F497D;}#yiv9174646187 .yiv9174646187MsoChpDefault
{font-size:10.0pt;} _filtered #yiv9174646187 {margin:1.0in 1.0in 1.0in
1.0in;}#yiv9174646187 div.yiv9174646187WordSection1 {}--> Albert the way I
think about it is, RUN SELECT is when I want to use it and a Stored Procedure
is used all the time. Buddy From: [email protected]
[mailto:[email protected]] On Behalf Of Albert
Sent: Tuesday, August 25, 2015 11:13 AM
To: [email protected]
Subject: [RBASE-L] - RUN SELECT or Stored Procedure? Glad that the RUN
SELECT worked for you!
My head cannot get itself around any difference between a RUN SELECT and a
Stored Procedure. Has anyone any idea when one is better than the other?
Albert On 2015-08-25 8:06 AM, [email protected] wrote:
CFA was for Custom Form Action. It is not related to compiling. You can
look in help
under CUSTOM and see the options for Custom Form Actions. A CFA is
basically an stored EEP that one can access multiple times from multiple places
in a form without duplicating the code lines. One could also think of it as
a stored procedure that is related only to the current form. The CFA
is called with the PROPERTY command such as : PROPERTY RBASE_FORM_ACTION
<CustomFormActionCommandName> <parameters> It is a very handy tool so one can
avoid duplicating code in multiple locations. This way, when the code does
need changed, you only have to change it in one location, -Bob From:
"Dan Goldberg" <[email protected]>
To: "ttc inc" <[email protected]>
Sent: Tuesday, August 25, 2015 8:26:40 AM
Subject: [RBASE-L] - Re: Button EEP versus Timer EEP Is a CFA a compiled
form application? What was the property command? Just want to make sure I
note this in the future. Thx Dan Goldberg From: [email protected]
[mailto:[email protected]] On Behalf Of Karen Tellef
Sent: Tuesday, August 25, 2015 5:57 AM
To: Dan Goldberg
Subject: [RBASE-L] - Re: Button EEP versus Timer EEP Big High Five from over
here!!! Glad it worked!
Karen -----Original Message-----
From: ttc.inc <[email protected]>
To: karentellef <[email protected]>
Sent: Tue, Aug 25, 2015 6:53 am
Subject: [RBASE-L] - Re: Button EEP versus Timer EEP I changed the code
from a CFA to a Run Select and everything ran perfectly last night. I did a
cut and paste of the code into the VarChar column, so there were no changes
in the operating code at all. Replaced the Property command with a Run
Select and this morning all was good. Not sure what the difference is.
I have in the past and have now, other apps that use the form timer eep and
CFA,s and they do not seem to have any issue. However, those CFA's have
1/4 the lines of code and no Delcare / While statements. Perhaps a
connection? Truthfully, I assumed that a CFA was pretty much a Run
Select command just build into the form designer. Thanks to all who
submitted ideas. -Bob From: "MikeB" <[email protected]>
To: "ttc inc" <[email protected]>
Sent: Monday, August 24, 2015 2:03:19 PM
Subject: [RBASE-L] - Re: Button EEP versus Timer EEP Let's wait to see
what happens with the Run Select before jumping out of the boat. >
-----Original Message-----
> From: [email protected] [mailto:[email protected]] On Behalf Of Karen
> Tellef
> Sent: Monday, August 24, 2015 2:10 PM
> To: [email protected]
> Subject: [RBASE-L] - Re: Button EEP versus Timer EEP
>
> Javier: I've seen Bob's app before, and it's a cool front-end type of
> form with lots of data for the users to see. The timer updates some of
> the data on the form.
> Let me think, if a scheduled task ran an "outside" RBase program, I
> guess it's possible that that program could dump the display data into
> a lookup type of table, and could still have a timer on the form that
> would gather and recalc the
> display. The form could have a "date last ran" / "date next run" so
> the user has
> some feedback on the process. A bit of work, but it would take the
> form out of the equation, wouldn't it?
>
>
> Karen
>
>
