Well, when people don't give sufficient details for us to help them debug,
sometimes we make guesses about what things could "probably be"; other
times, we politely ask for more information; some times, fed up to the ears
with "something went wrong, fix it for me", we just close the question and
move on.
"Niall Litchfield" <n-litchfield_at_audit-commission.gov.uk> wrote in message
news:3c88a4fa$0$233$ed9e5944_at_reading.news.pipex.net...
> "David W. Fenton" <dXXXfenton_at_bway.net> wrote in message
> news:91CABF804dfentonbwaynet_at_news-server.nyc.rr.com...
> > Creating poorly performing drivers for standard interfaces in order
> > to force customers to use a proprietary tool is not a "customer
> > retention" strategy. Well, it wouldn't be for me. It's precisely
> > the kind of thing that would drive me to purchase from a different
> > company entirely.
>
> Hmm VJ++ anyone? A poorly performing non-standard extension to a
> cross-platform standard created specifically to bury the competition.
>
> Seriously. As I said the oracle ODBC drivers are not poor. They are fine.
> The MS provider for oracle though doesn't seem to advanced much if at all
in
> the last few years. Whilst I understand the MS reasons for this the OP
never
> stated that he was using Oracle ODBC drivers just that he was accessing
> Oracle using ODBC.
>
>
> --
> Niall Litchfield
> Oracle DBA
> Audit Commission UK
> *****************************************
> Please include version and platform
> and SQL where applicable
> It makes life easier and increases the
> likelihood of a good answer
>
> ******************************************
>
>
Received on Fri Mar 08 2002 - 11:26:12 CST
