No, its 32-bit Vista.

Since I posted that message I have heard that there is an issue with the VFPOLEDB.DLL being stopped by a Vista feature called Data Execution Prevention. Apparently there is a way to add the DLL to the DEP exception list and that could allow it to work. However, his system blue screened on reboot and he had to format his drive. So he gave up Vista all together.

I have not tried changing my DEP exception list myself. Anyone else have any experience with this?

I have been experimenting with the Advantage drivers for VFP. From what others have said it seems that it might be best to avoid VFPOLEDB.DLL all together.

>You wouldn't be using 64-bit Vista would you?
>
>>I am trying to access VFP tables from VS2008. Any attempt to use the OLEDB Provider for Visual FoxPro crashes VS2008.
>>
>>For example if I do the following:
>>1) Go to Tools->Connect to Database
>>2) Select in Dats source list box.
>>3) Set .NET Framework Data Provider for OLE DB
>>4) Click Continue
>>5) In the OLE DB Provider drop down select Microsoft OLE DB Provider for Visual FoxPro
>>6) Click Data Links
>>
>>I will get the message "Attempted to read or write protected memory. This is often an indication that other memory is corrupt." VS2008 is then hung and must be closed from the task manager. I am also running on Vista Business.
>>
>>I found message #1301223 which describes the same problem. So I know I am not the only one having this issue. Has anyone come across a solution for this? Or is anyone using the VFP OLE DB provider on Vista with VS2008 with out problem?