🚀 go-pugleaf

Oracle has its own OLEDB provider and another OLEDB provider is included in 
MDAC (Microsoft Data Access Components, setup for OLEDB/ADO). The first one 
should be distributed with your application, second is installed yet on most 
computers or can be installed with MDAC. MS SQL Server is one of DBMS ADO 
was developed for, OLEDB provider for it is included in MDAC.

//------------------------------------------
Regards,
Vassiliev V. V.
http://www.managed-vcl.com - using .Net objects in Delphi for Win32 + 
ADO.Net
http://www.oledbdirect.com - The fastest way to access MS SQL Server,
MS Jet (Access) and Interbase (through OLEDB)

"Foo Tze Wan" <twfoo@nospam.com> �������/�������� � �������� ���������: 
news:4303e931@newsgroups.borland.com...
> Thanks, Arnie for your reply.
>
>>It's more like "ADO over ODBC", and yes, you can do it, though
>>most will recommend against it.  MS provides an OLEDB driver for
>>"generic ODBC".  It can be used with Borland's ADO.  You'd
>>probably be better off using the OLEDB provider supplied by the
>>manufacturer if you support other DBs.
>
> The reason why I thought my application should retain ODBC connectivity to
> databases is because these databases are ODBC compliant only, but not 
> OLEDB.
> (Perhaps, I have not been in tune with newer data access technologies.) 
> The
> databases we envision we will be using are Oracle and SQLServer. After 
> some
> brief searces on the web, I think they should also support OLEDB.
>
>>If you go with ADO, you'll have to do sime fiddling with the
>>query or dataset properties in order to get good performance.
>>These include cursor location and type as well as locking mode
>>and cache size.
>
> I will try with ADO, and when these issues arise, will grapple with them. 
> I
> hope help from here and the web can be easily found then.
>
> Thanks again,
> Tze Wan
>
>