hi All,
I have following "package" and "stored procedure",I want to run this procedure from vb6, can anybody tell me what will be the "vb6 code" for the following procedure

----------------------------------------------
CREATE OR REPLACE PACKAGE BODY pgarage AS

  PROCEDURE prcempmst(empno IN VARCHAR2, empname IN VARCHAR2, basicsal IN INT, POSITION IN VARCHAR2, p_recordset OUT sys_refcursor) AS
  empmast empmst%rowtype;

  BEGIN

    OPEN p_recordset FOR SELECT*FROM EMPMST WHERE empid=empno;
    fetch p_recordset into empmast;

    IF empmast IS NULL THEN
      INSERT
      INTO empmst
      VALUES(empid, empname, basicsal, POSITION);
    ELSE
      UPDATE empmst
      SET empid = empid,
        empname = empname,
        basicsal = basicsal,
        grade = POSITION;
    END IF;


  END prcempmst;
end pgarage
-------------------------------------------------

To use a stored procedure, you:

    Create and open a connection object
    Create a command object, Setting its type to stored procedure.
    Set the command text to the name of the procedure
    Set the ActiveConnection to the connection that you opened
    Create a parameter for each argument in the stored procedure
    Set the parameter's variable type, whether it is IN or OUT
    Set the parameter's value, if appropriate
    Append it to the command object.
    Repeate that for each parameter

Once everything has been set up, use the command object's .Execute method to actually run the procedure. The OUT parameters of the command object will hold the values put into the OUT parameters of the stored procedure.

Be sure to close everything properly when you're done.

Thank you very much for your reply,

Can u please tell me what is the use of closing the objects like recordset and connection,

rs.close ' ok this line is use full

set rs=nothing ' why we are using this line without this also program will work can please tell me

The program will work fine without explicitly closing objects, and releasing all references to them——probably...

But explicitly closing and releasing makes the intent clear when reading the code, and prevents accidentally leaving a global reference to an object messing things up.

Let's say you open a connection, and then mistakenly set a global object to hold a reference to it. The program's refernce count for that connection will = 2. Leaving the sub will eliminate one of them, but the other will still be valid. If you never closed the connection, it will stay open.

Explicitly closing it will at least make it so that it does not stay open. Leaving the routine will reduce the reference count by one, leaving it at 1.

But that is a better situation than having the connection count too high by one [u]and</u> having the connection not be closed.