Are you passing the correct constants with the parameters?

Set prmParam = .CreateParameter("out_result_cd", adInteger, adParamOutput, ,
0)

	I'm just wondering if you're specifying adInteger and adParamOutput.

	Crap.  You're using RDO.  For some reason I don't think the above code
could be of any help to you, unless you upgraded your RDO to ADO (highly
recommended!).

? Chuck

> -----Original Message-----
> From: h.prochaska@n... [mailto:h.prochaska@n...]
> Sent: Monday, May 14, 2001 7:30 AM
> To: professional vb
> Subject: [pro_vb] ActiveX COM object argumnets (Variant InOut) with
> Visual Basic
>
>
> I ahve to develop an ActiveX component (.exe or .dll) to access Oracle
> stored procedures returning values. I have written that in Visual Basic
> 6.0 using RDO and it works fine stand alone. Now I have to call this COM
> object from an eviromnet which is unable to process arguments of type
> Variant InOut. Does anybody have an idea how to force Visal Basic not to
> produce Variant type variables and to declare arguments as Out only. I am
> working with option explicit and have declared all variables with the
> correct type, but in the Interface they always appear as Variant InOut.
>
> Kind Regards
>
> Heinz