OK. Sorry Asif. I guessed I must've missed part of the thread. I don't know what the answer to that is because I have no way of testing it on a PC that doesn't have VFP7 installed. And right now, that won't be an issue for us, as we have a SQL Server back end and won't be messing with VFP data anyway, so I don't know if I'll ever get around to testing it out.

I hope someone has some other suggestions for you to try.

Good luck.

~~Bonnie


>Yes, it does work with .NET only if VFP7 is installed on the same machine. Also here, let me make it clear. If I manually set the OleDBConnection object and OleDataAdapter on a machine without VFP7, I can preview the data in the VS.NET design environmment. However, If I try to programatically instantiate the required OleDB objects and try to OPEN a connection, the program fails. If I then install VFP7, the program works without my having to change a single line of code.
>
>I have built all possible combinations of the Installer with VFP OLEDB Provider, MDAC26ENU, VFP Runtime. But still I cannot get it to work on a machine that does not have VFP7 installed. The moment I install VFP7, everything works. I tried this on three different machines (W2K SP2, NET Runtime, QPatches, IIS) and no luck until VFP7 is installed.
>
>The Merge Module description for VFP OLEDB Provider claims that it makes all the required registry entries.
>
>>Asif,
>>
>>I wouldn't give up on the VFP OLEDB Provider so quickly if I were you. It *does* work with .NET, I have used it. I'm assuming that you still have something configured incorrectly, but unfortunately I don't have any quesses as to what that might be ....
>>
>>~~Bonnie
>>
>>>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.