>>>>I must admit that I'm a bit biased against using either of these drivers and prefer moving data to SQL Server instead.
>>>>
>>>>I'm pretty darn sure that the VFP ODBC driver is not thread-safe. What about the VFP OleDb driver? I've actually never used it. How does it hold up when used by WCF services? How robust is it?
>>>>
>>>>Ideas on either of these two drivers is appreciated.
>>>
>>>VFP ODBC driver is thread-safe.
>>>http://msdn.microsoft.com/en-us/library/ms709357(v=vs.85).aspx
>>
>>Victor,
>>
>>With all due respect, there is a KB article that says the following:
>>
>>"The problem with this design is that the Visual FoxPro ODBC driver is not thread-safe, and as a result, MTS/COM+ (or the objects themselves if they are stand-alone) can fail."
>>
>>See: http://support.microsoft.com/kb/288863
>>
>>I've seen your KB and I can't believe what it says. I think there's a lot of confusion going on around the VFP ODBC driver. When I was at MS I tested the VFP ODBC driver and found that it was not thread-safe. And I think by design it was not thread-safe.
>
>hmmm... well there is this too from the VFPODBC.txt:
>The driver is thread-safe. The Visual FoxPro ODBC driver can process queries in the background. For more information, see the "ODBC Visual FoxPro Setup Dialog Box" Help topic. Maybe Rick Schummer will know for sure - like you said there is a bit of confusion on this one...


My 2001 version of VFPODBC.txt says the following with MS emphasis on the NOT:

2.4 Thread Support
==========================
The driver is NOT thread-safe. The Visual FoxPro ODBC Driver can process queries in the background. However, you should disable this feature if the driver is being called by a multi-threaded application. For more information, see the "ODBC Visual FoxPro Setup Dialog Box" Help topic in DRVVFP.CHM or in the detailed help file.

I'm glad that Microsoft is consistent on this matter.