Duey, To the best of my knowledge "RETURN INTEGER" in PUT command is valid syntax.
Jim Bentley --- "Heffelfinger, Duane" <[EMAIL PROTECTED]> wrote: > Now that I've read everyone's email it appears as though I may > have > tried something that may not be correct. My put statement is > as > follows: > > PUT g:\database\prcfiles\AdmActCnvPrc.prc + > AS AdmActCnvPrc + > vpActCv_Refnum TEXT (9) + > RETURN INTEGER > > I suspect as Razzak suggested I should have used RETURN TEXT > or RETURN > TEXT (20) and not RETURN INTEGER. While it worked initially > it also > caused my problems with other procedures. > > Thanks again to everyone for you input. I now know more about > stored > procedures. > > Duey > > > > > > -----Original Message----- > From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf > Of > Heffelfinger, Duane > Sent: Wednesday, May 21, 2008 10:10 AM > To: RBASE-L Mailing List > Subject: [RBASE-L] - STP_RETURN Variable when running a > procedure > > Good morning, > > As usual I'm probably missing something very simple here, but > I've had > some trouble running procedures one after another due to the > STP_RETURN > variable. Basically what happens is: > > Procedure 1 returns an INTEGER > Procedure 2 returns a TEXT > > When I run procedure 2 it fails because procedure 1 created > the variable > STP_RETURN as integer. > > While I think there are two simple answers: > > 1. CLEAR VAR STP_RETURN before I run any procedure > 2. Have all procedures return a value of TEXT (????) to ensure > a large > enough text variable for any procedure > > My question is: What is the best practice or am I missing > something > easier? > > Duey > > > Jim Bentley American Celiac Society [EMAIL PROTECTED] tel: 1-504-737-3293
