> C) OLE normally relies on ODBC, again performance issues.
Yes that is correct, if you have a straight ADO/OLE DB then it does not use
ODBC - unless of course the ADO/OLE DB vendor has built their driver on top
of their ODBC code - but then no one except the vendor knows that.
Perhaps an even bigger issue with ADO is the Locking/Cursor mechanisms and
how the ADO driver implements these given the Interbase multi-generation
record mechanism.
Perhaps the biggest plus with ADO would be if you write everything using
stored procedures you could just by changing your provider string substitute
another backend DB. Again I suspect this would have a performance issue do
the ADO locking and ADO cursor models - i.e. the model you use with IB is
unlikely to be optimal for another ADO provider - Ah well ...
Myles.
-----Original Message-----
From: Paul Ritchie [mailto:[EMAIL PROTECTED]]
Sent: Thursday, 2 August 2001 5:36 p.m.
To: Multiple recipients of list delphi
Subject: RE: [DUG]: Delphi to Interbase access options
I've seen that posted before, however I believe OLE DB actually replaces
ODBC and usually provides better performance.
An OLE DB provider for ODBC is provided in the MDAC for backward
compatibility, but neither technology "relies" on the other.
Paul Ritchie
Radio Computing Services
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
To UnSub, send email to: [EMAIL PROTECTED]
with body of "unsubscribe delphi"
Web Archive at: http://www.mail-archive.com/delphi%40delphi.org.nz/
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
To UnSub, send email to: [EMAIL PROTECTED]
with body of "unsubscribe delphi"
Web Archive at: http://www.mail-archive.com/delphi%40delphi.org.nz/
