ThanksLarry for responding. This sound dumb and maybe it is, but here goes.

1. In the Report Manager, like previously mentioned, I select ADO and click configure.
2. Data Link Properties opens up and I get to select: Microsoft OLE DB Provider for ODBC Drivers.

Q1. This means I am using OLE DB. OLE DB in turns calls the ODBC driver for VFP?
Q2. Is there any place where OLE DB for VFP downloadable?

Please advise.

>Let me start by stating that I don't know if the VFP 8 OLE DB provider will work for a VFP 6 DBC. My guess is that it would.
>
>Because you are using ADO, you can use the OLE DB provider as your connector. You simply need to use the appropriate connection string for your ADO Connection object. See Message#727577 for an example.
>
>HTH.
>
>>Hi Larry.
>>
>>I am barging in. But I have this situations. I used VFP6 SP5 database / views / tables. I also use Report Manager which uses currenctly ADO to connect using ODBC to the VFP DBC.
>>
>>How can OLE DB play a role in such a situation.
>>
>>>>Does anyone know if the bug described in this KB article has been fixed or not? Any workarounds?
>>>>
>>>>http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B275577
>>>
>>>Jayesh,
>>>AFAIK, the ODBC driver has not been updated since 6.0. Once the OLE DB provider was available, resources were diverted away from the ODBC driver.
>>>
>>>The work around would be to break your remote views up into field lists of less than 65 columns. You could duplicate the key fields in each view and have a different subset of fields to update.
>>>
>>>HTH.