You should be thinking differently and go to n-tier, not two-tier (typical client/server). There is no direct data access to SQL Server, it's all done via SQL commands. Here are some articles on SQL/VFP, but most talk about two-tier apps.

http://msdn.microsoft.com/archive/en-us/dnarfoxgen/html/msdn_bko01.asp
http://msdn.microsoft.com/archive/en-us/dnarfoxgen/html/msdn_fpsqlcs.asp
http://msdn.microsoft.com/archive/en-us/dnarfoxgen/html/msdn_bko02.asp
http://msdn.microsoft.com/archive/en-us/dnarfoxgen/html/msdn_usevfp.asp
http://msdn.microsoft.com/library/en-us/dnfoxgen/html/adojump.asp
http://msdn.microsoft.com/library/en-us/dnsql2k/html/sql_embeddingmsde.asp
http://www.spacefold.com/colin/archive/articles/sql_backend/backend.htm

There are some sample chapters you can download from http://www.hentzenwerke.com/catalog/csvfp.htm

For n-tier, you may want to look at web services or COM+. See the articles on my web site.

>Hi
>
>Does anyone have a generic VFP application that uses SQL2000 as its back-end? I want to upsize my current VFP applications to an SQL back-end, from the native VFP, so it'd be useful to see someone elses code to see how they've tackled the problems associated with the changing of the back-end.
>
>My current applications do quite a bit of SQL, and many of the forms objects (textboxes etc) are tied directly to the VFP tables; I wonder how this would be done with data from an SQL Server????
>
>I'd also like to see examples of embedded SQL Server code, i.e. calling/running stored procedures in SQL Server to perform reports, data look-ups etc, generic read/write routines.
>
>Ultimately I'd like to have ALL SQL statements within SQL Server as the platform will not only be used by VFP, but by various web-enabled applications in .net and VB.
>
>Any help/pointers would be gratefully received.
>
>Regards