To be exact, SQL Server is deprecating OLEDB, which I suppose is pretty much the same thing, but existing OLEDB drivers for other databases will continue to work. In this case, I'm interested because the Excel ODBC driver assumes the first row contains column names, and I need to import a file where the first row contains data. There is a setting to override this behavior, but there is a bug in the driver and it doesn't work (http://support.microsoft.com/kb/288343). This bug has been around for many years, and even though they added XLSX support to the ODBC driver, they still haven't fixed the bug! The setting in the OLEDB driver works, so I was hoping to use it without having to use ADO.

>I don't think so, You can go the other way, but not sure why you would want to. Also, keep in mind that Microsoft has declare OLEDB to be dead.
>
>>Is it possible to connect to an OLEDB provider using ODBC? I always assumed that required ADO, but I found the code below in Craig Boyd's AppendXLSX.prg. Unfortunately, it pops up a dialog for me to select a data source, so I'm curious if this would have worked for Craig or anyone else.
>>

>>m.lnSQL = SQLSTRINGCONNECT([Provider=Microsoft.ACE.OLEDB.12.0;Data Source="] + m.tcXLSFile + [";Extended Properties="Excel 12.0 Xml;HDR=] + m.lcHeaderRow + [;";])
>>