Larry, No, but I did discover that I was calling some procedures without a variable to populate from the RETURN value of the procedure as below. While I didn't need the returned value from some procedures, I suspect that's what caused my problems.
(CALL ProcName(. .. )) Instead of SET VAR vvar INTEGER = (CALL ProcName(. .. )) Thanks so much for taking the time to consider what I may be doing wrong. Duey P.S. If you copy and run the sample code below, I suspect you'll get the results I was seeing. --START --temp1.prc OUTPUT temp1.prc WRITE 'RETURN 1' OUTPUT SCREEN PUT temp1.prc + AS Temp1Prc + RETURN INTEGER --temp2.prc OUTPUT temp2.prc WRITE 'RETURN Duey' OUTPUT SCREEN PUT temp2.prc + AS Temp2Prc + RETURN TEXT SET ERROR MESSAGES ON CALL Temp1Prc () CALL Temp2Prc () --END -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Lawrence Lustig Sent: Wednesday, May 21, 2008 1:40 PM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: STP_RETURN Variable when running a procedure Duey: How are you calling the stored procedure? You're not doing this, are you: SET VAR STP_RETURN = (CALL ProcName(. .. )) ? -- Larry
