Thanks for the offer but I need to be able to update the source table also.
No matter. I have come to expect this kind of road block with anything related to FoxPro and started moving away from FP a couple of years back.
I still cannot understand why someone would create a VFP OLEDB Provider for VFP users only? M$ documentation implies that any .Net client can use it.
It will take me a day to convert the existing VFP application to VB, and I have already confirmed that I can access an Access 2000 database via the Jet 4.0 OleDB Provider and C# client.
I appreciate the help of all those who responded to this thread.
Thanks.
>I tried to use it too. Never got it to working. Also, ODBC.NET providers are not tested for Fox drivers, hence doesn't make sense to use it in a production app.
>
>Though, I wrote a simple code that gets XML from Fox and converts it to DataSet in .NET..Send me an email if you are interested...
>
>>I cannot seem to connect to a VFP database using the oleDbConnection object.
>>
>>I have setup an ODBC connection to the directory that holds the free VFP tables and I am using the oleDbConnection object to access the tables via the "Microsoft OLE DB Provider for ODBC Drivers" which connects to the ODBC connection.
>>
>>How do I connect to a DBF table using ADO.NET?
>>
>>I get the following error:
>>
>>The .Net Data OLE DB Provider(System.Data.OleDb) does not support the MSDASQL Provider, Microsoft OLE DB Provider for ODBC Drivers.
Précédent
Suivant
Répondre
Voir le fil de ce thread
Voir le fil de ce thread à partir de ce message seulement
Voir tous les messages de ce thread
Voir tous les messages de ce thread à partir de ce message seulement