Re: Input array string

I can't say whether what you describe used to work or not, I never did VB + ADO + Oracle.

I can say with certainty that it doesn't work that way now, in ADO.NET.

Sure would be great if it did, but it doesn't.

"Mark C. Stock" <mcstockX_at_Xenquery .com> wrote in news:pfCdnWADNMWjnIrdRVn-vA_at_comcast.com:

>
> what i'm recalling from by VB ADO days was that the driver provider
> automatically translated a VB array into the PL/SQL table expected by
> the stored procedure -- i'm quite sure this was possible for both
> input and output.
>
> so there was no special syntax on the VB side, no need for VB to know
> anything about that the stored procedure used PL/SQL objects and not
> VB objects, it was all done by the driver
>
> unfortunately, it's been quite a few years, so i don't have any of the
> references right handy, but i can't imagine something that was
> possible 5 or 6 years would not be possible with MS's 'new and
> improved' toolset
>
> -- mcs
>
>
>
Received on Tue Jan 27 2004 - 18:36:00 CST