storedProcmethod of the
databaseobject or of a
Connectionobject. You do not call a
Stprocobject, use the
closemethod to close it and release the memory it uses. If you release a connection that has an open stored procedure, the runtime engine waits until the stored procedure is closed before actually releasing the connection. If you do not explicitly close a stored procedure with the
Connectionobject goes out of scope. This can tie up system resources unnecessarily. It can also lead to unpredictable results. You can use the
prototypeproperty of the
Stprocclass to add a property to all
Stprocinstances. If you do so, that addition applies to all
Stprocobjects running in all applications on your server, not just in the single application that made the change. This allows you to expand the capabilities of this object for your entire server.
majorErrorMessagemethods to interpret the cause of the error.
closemethod closes a stored procedure and releases the memory it uses. If you do not explicitly close a stored procedure with the
clientobject goes out of scope.
outParameters, to ensure that the stored procedure has output parameters.
outParamCountmethod before you call this method. If
outParamCountreturns 0, the stored procedure has no output parameters. In this situation, do not call this method. You must retrieve result set objects before you call this method. Once you call this method, you can't get any more data from a result set, and you can't get any additional result sets.
resultSetmethod. See the description of the
Resultsetfor restrictions on when you can use this method access the result sets for a stored procedure.
spobj = connobj.storedProc("getcusts");
// Creates a new result set object
resobj = spobj.resultSet();
Last Updated: 11/13/98 10:23:53