Yep. ODBC for .NET. However, if I were writing a .NET data provider for 
Paradox for MS SQL Server I'd use the native SQL server connectivity 
built into Visual Studio and not stuff around. For other databases, I'd 
use the .NET drivers from the database vendors who keep their drivers up 
to date (e.g.NpgSQL) and not support a database whose ODBC driver was 
last updated in 1998. As Microsoft deprecates ADO the major database 
players will move to the latest MS standards.

Leslie wrote:
> Tom,
>
> Commencing in 2011, Microsoft announced that OLE DB (and thus impacting ADO)
> is being phased over a&  year period.
> They are refocusing on, drum roll..........., yes you guessed it, ODBC.
>
> Here is a link:
> https://redmondmag.com/articles/2011/09/01/microsoft-shifting-to-open-database-connectivity-for-sql-server.aspx
>
> So what is old is new again
> Leslie.
>
>