Ummmmm . . . AhHa, wait. Are we talking about System.Data.OleDb with the provider being "Provider=VFPOLEDB.1"? In which case, that's what I have used lately without giving it any thought other than "ODBC warmed over".

>Ummm... OK... but the .Net Data Provider is faster and uses managed code. Plus, there's no interop.
>
>>Good point, good question.
>>
>>First, I've used ODBC and now OLE DB in other areas and am "familiar" with it - in the same way somebody might be familiar with an alcoholic acquaintance, you know them but don't want to know them too well.
>>
>>And then, I'm only using OLE DB until the applications are fully converted to MS SQL Server (or PostgreSQL in one case) and then there will be no foreseeable use.
>>
>>Finally, if someday in the future I have a need a bridge from one format to another I would look around for something more up to date - especially if OLE DB is dropped.