RE: Witango-Talk: Problem with Stored Procedure

[Ben Johansen]

Hi,   I would say that the 2nd line of the message pretty much sums it up. when you write stored procedures the need to be self contained and ask nothing from end users.   I noticed that your procedure doesn't take any input ie. select (call proc5('param'))   does it return a value ie an integer or small text to tell the calling program that it worked.   It is hard to tell you what exactly went wrong without seeing the code.   -info- Stored procedures are made up of SQL commands and R:BASE commands except for: CODELOCK FORMS RBEDIT RESTORE CONNECT PACK RBLABELS RULES DISCONNECT PLAYBACK RECORD SET (without a keyword) EXPRESS RBDEFINE REPORTS TRACE Also, do not include commands that change the structure of your database or change access rights. Ben Johansen - http://www.pcforge.com Authorized WiTango Reseller http://www.pcforge.com/WitangoGoodies.htm latest beta downloads @ http://www.witango.ws    -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Benjamin Strickland Sent: Sunday, October 20, 2002 7:45 AM To: Multiple recipients of list witango-talk Subject: Witango-Talk: Problem with Stored Procedure Why do I get this message when I test my stored procedure?   This SQL has been generated by the action " SP1" : SELECT (CALL PROC5( )) FROM STOREDPROC WHERE PROCNUMBER=1   [Query]  SELECT (CALL PROC5( )) FROM STOREDPROC WHERE PROCNUMBER=1 2136 [RBTI][Oterro ODBC Driver][Grade Management System]-ERROR- Insufficient buffer space to process expressions. S1001 2557 [RBTI][Oterro ODBC Driver][Grade Management System]Illegal command in Entry/Exit Procedure. S1000