There definitely is a problem with the VFP ODBC driver.
On local machines the VFP ODBC driver works as advertised.
(At least I haven't found any problems.)

Try using the ODBC driver from one server to another server.
It just doesn't work. MS Knowledage Base article ID Q175801
deals with this. We haven't tried it yet and won't try
it until after Thanksgiving weekend (next week).

Strangely enough, MS Access has the same problem. ODBC works
great on local servers but not remote servers. So I guess it
is a problem with the ODBC drivers across the board.

If someone has found an easy workaround, please post it.


>>I'm not sure I explained my self properly regarding writing to vfp tables via ODBC. I know I can build a VFP app and write via ODBC to other data sources (access, excel etc...) But I've been told I couldn't write a VB app for instance and use ODBC to write to VFP tables. In fact another reply in this thread confirms that there is a Knowledgebase article (which I have yet to look for) confirms that this.
>
>That's a big pile of BS, and here's the VB code I tested:
>Assumptions:
>1) You have created a DSN that points to a free table directory, which is based on the Microsoft Visual FoxPro Driver version 6.0
>2) You have a free table called "Temp" that has one field of type character.
>

>Private Sub Command1_Click()
>  Dim oCn As New ADODB.Connection
>  oCn.Open "DSN=Visual FoxPro Tables"
>  oCn.Execute ("Insert Into Temp Values ('whatever')")
>  oCn.Close
>  Set oCn = Nothing
>End Sub
>