I can think of two reasons

- OLEDB goes through the COM layer. It's very likely faster and uses less memory to go through ODBC

- Microsoft is dropping OLEDB. At some point they won't update the Jet OLEDB Provider. Then you'll either a) be forced to stay with older versions or b) Be in crisis mode trying to rewrite for ODBC.


>This is an isolated process which is not part of the framework data dictionary, thus accessing that table is disconnected from the regular environment. To make it work, an example was found on the net and it seemed everyone was using the same approach from .NET to access a DBF. There is a new 64-bit driver and I believe the developer is using it presently. I still haven't had the chance to verify the results. What are the advantages of using that one over the other?