Y'all are right. I actually slowed down enough to take a peek at Razzak's "Tip of the Day" PDF and, voila e voici, eureka, boom, there it is:
5.1 Controlling the Maximum Length of the RETURN Variable The returned value is stored in the STP_RETURN system variable. The RETURN varname option is used ONLY within a Stored Procedure to return a value. This option will return an -ERROR- when used outside a Stored Procedure. The default is TEXT 8 characters, but if you want more, you can set it to a larger value. You can control the maximum length at procedure definition time, or by editing the SYS_PROC_LEN column in SYS_PROC_COLS system table. Example 01: PUT MyTest.PRC AS MyTest P1 INTEGER RETURN TEXT (30) This will set the limit for the RETURN value at 30 characters. I guess "currency" as in, "... it pays to stay current ..." goes beyond just the version-number. Now, back to find something else I surely missed! Steve in Memphis -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Ken Sent: Tuesday, February 19, 2008 6:57 PM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: Forget That Crosstab for Now,My STP_RETURN Is Truncating MyValue To add one more comment. To fix the issue you have to use the "PUT" command to initially create the stored procedure from a file. Make your return arg and length as big as needed. After that the database explorer can be used to edit and trace the procedure. Regards, Ken James Bentley wrote on 2/19/2008, 6:42 PM: > Steve, > > Amplifying Dennis's comment. To the best of my knowledge if you > don't specify a data type for "RETURN" in the PUT command it > defaults to TEXT(8). > > Jim > --- Dennis McGrath <[EMAIL PROTECTED]> wrote: > > > Check your stored procedure definition. I'll bet the return > > datatype is TEXT (8) > > > > Dennis McGrath > > > > -----Original Message----- > > From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf > > Of Wills, Steve > > Sent: Tuesday, February 19, 2008 4:06 PM > > To: RBASE-L Mailing List > > Subject: [RBASE-L] - Forget That Crosstab for Now, My > > STP_RETURN Is Truncating My Value > > > > Don't know why, but, as shown below, the values I'm trying to > > return via > > my Stored Procedure CALL are being truncated. Any ideas? > > > > Thanks, > > Steve in Memphis > > > > > > R>SELECT Proposal_Number,(CALL > > CHK_4_AWARD(Proposal_NUMBER))=16 FROM > > R_PROPOSAL WHERE PROPOSAL_NUMBER LIKE '0806%' AND > > SEQUENCE_NUMBER = > > (SELECT MAX(SEQUENCE_NUMBER) FROM R_PROPOSAL r WHERE > > r.PROPOSAL_NUMBER=R_PROPOSAL.PROPOSAL_NUMBER) AND LIMIT=10 > > Proposal (CALL CHK_4_AWAR > > -------- ---------------- > > 08061541 010847-0 > > 08061542 010847-0 > > 08061543 010847-0 > > 08061544 010847-0 > > 08061545 010847-0 > > 08061546 010847-0 > > 08061547 010847-0 > > 08061548 010830-0 > > 08061549 010830-0 > > 08061550 010830-0 > > Columns have been updated in 1 row(s) in SYS_PROCEDURES > > Successful INSERT operation, 1 rows generated. > > > > R>sho var > > Variable = Value > > Type > > ------------------ ------------------------------ > > -------- > > #DATE = 02/19/2008 > > DATE > > #TIME = 16:02:58 > > TIME > > #PI = 3.14159265358979 > > DOUBLE > > SQLCODE = 0 > > INTEGER > > SQLSTATE = HY000 > > TEXT > > #NOW = 02/19/2008 16:02:58 > > DATETIME > > STP_RETURN = 010830-0 > > TEXT > > vMIT_AWARD_NUMBER = 010830-001 > > TEXT > > viMAN = 0 > > INTEGER > > > > J. Stephen Wills > > Program Manager, Research Informatics > > Office of the Vice Chancellor for Research > > University of Tennessee Health Science Center > > 62 S. Dunlap, Suite 400 > > Memphis, TN 38163 > > Office: 901-448-2389 > > FAX : 901-448-7133 > > > > > > > > > Jim Bentley > American Celiac Society > [EMAIL PROTECTED] > tel: 1-504-737-3293 > > > > ________________________________________________________________________ ____________ > > Be a better friend, newshound, and > know-it-all with Yahoo! Mobile. Try it now. > http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ > >
