Re: Is it possible using stored procedure like this way???

In article <ceqkvj$lv6$1_at_sunnews.cern.ch>, dominique_hung_at_hotmail.com says...
> Hi Tom,
>
> Thank you for reply.
>
> 1. I changed the inputparam type to adVarChar, but I got the same error
> message
>
> 2. The 128 on the Execute line means adExecuteNoRecords. Because someone
> says
> if a recordset was being returned from the Execute method then it'd be
> assigned to
> recordset object. As my code doesn't return a recordset, I suppose I can
> use the
> adExecuteNoRecords.. Even I tried Comm.Execute in stead of
> Comm.Execute,,128,
> I got the same error message..
>
> Do you have any idea???
>

You'll have to take a step back then and check the following:

• can you call the procedure with SQL*Plus as user "test"? Perhaps the package is in another schema?
• I would then put together a small VB test program (not VBScript or ASP, just a standard .EXE) and test database access with that. That way it's isolated and you can use the normal ADO object model, and not just plain old CreateObject.

Have you considered switching drivers? Microsoft drivers for Oracle are pretty lame you know.

• Tom