Re: Using bind variables with VB and ADO but viewing SQL_AREA shows non-bound parameters

"Jane O" <janeohin_at_aol.com> wrote in message news:b9tur7$jm8$2_at_reader1.panix.com...
> That is RIGHT.....
> The "rule" is pretty simple - When it comes to Oracle development...if you
> want best integration, scalability,
> , performance, best usage of Orace features, maintemance....just FORGET
> about M$ stuff....just forget it......
> , use VB ONLY for what it is...a GUI build tool....don't let it or ODBC,
> ADO....talk to Oracle....it's a LOST case
> M$ and Oracle just don't like each other...
>
> My OO4O app don't need no odbc driver....don't care if the machine has the
> lastest ADO.....just runs
> and talks happily with Oracle.

No it just requires an OO4O driver, which you are only likely to be able to guarantee in a corporate environment where you can mandate the build.

Don't get me wrong I'm not trying to knock OO4O, but I don't buy the assertion that ADO/OLEDB/ODBC is a 'lost cause' if it were our corporate intranet wouldn't have been running successfully for the last 5 years. Specific error messages that can be shown to be a result of MS tools interfacing badly with Oracle - rather than coding errors I might be convinced by, bald statements that MS tech and Oracle databases don't work together seem to me to be just plain wrong.

> Another advice: NO DDL/DML in VB....use package/stored objects.

That I agree with entirely, but its hardly VB specific advice.

--
Niall Litchfield
Oracle DBA
Audit Commission UK