There is an OLEDB provider for SQL but to be honest you are probably better
sticking with ODBC if you are using ColdFusion as the development tool.  I
don't think you are that restricted by using an ODBC DSN.  You may want to
use OLEDB if you are say creating connections on the fly in code e.g. ASP.
It will enable you to connect to all different kinds of data sources (in
fact anything that has a OLEDB provider written for it)

If you want to see a good article explaining how OLEDB works compared to
ODBC and ADO/RDO/JET/etc.....then have a look on the Microsoft site or buy
the book "Hitchikers Guide to VB^ and SQL Server 7" - A very good read
although not needed for CF development!

-----Original Message-----
From: Brian Mitter [mailto:[EMAIL PROTECTED]]
Sent: 03 August 2000 11:21
To: [EMAIL PROTECTED]
Subject: oledb and native drivers


Hi All,

    Can someone explain the difference between oledb and native drivers for
connecting to datasources?

In the CF Administrator there seems to be native drivers for Sybase11,
Oracle73, Oracle80, Informix83 and DB2. Should there be one for MS SQL? In
the oledb section of the administrator there is sqloledb and microsoft jet.

We are using CF Enterprise 4.01 and MS SQL 7.0 What is the best way to
connect to the datasources on the SQL server? Any url's for more reading
matter on oledb and native drivers? Ive tried the Allaire site but the
search is still down.

Thanks in advance
   Brian


----------------------------------------------------------------------------
--
Archives: http://www.mail-archive.com/[email protected]/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/[email protected]/
To Unsubscribe visit 
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a 
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.

Reply via email to