>FoxPro's default does not share connection on remote view automatically. You must make sure of this yourself.
>

Found that, thanks.

>If you open a view which uses a shared connection, then you can read it's connection handle and you have a shared connection number which you can use for SPT commands. Be aware that this connection number will only be valid if you have one or more other views open which have used the connection. Once you close the view(s), the handle is no longer available for SPT.
>

Ok. That seems easy enough.

>Processing happens on the local PC. Triggers, etc. will still fire. You need to take precautions and make sure you don't put code in your triggers that have any UI. Also, you should experiment carefully with your [trigger] stored procedures because teh ODBC driver does not support the full language set of VFP and the help file (DRVVFP.HLP) is not always clear. Also, default values are not supported through the ODBC driver (if I remember correctly).
>
>

Just read thruough the DRVVFP.HLP file. Couldn't find it earlier. It looks like Next week is play with ODBC week :)

>Working with the ODBC driver will take more time than traditional VFP programming. Plan for the extra time.
>
>One other point I can make is that if you are careful with table names, field names, datatypes, etc., when you move to SQL Server, most of your code can remain 100% unchanged. It can be a snap if you've planned ahead.

Good advice. As I am rather new to VFP that can be a little trying at times. Everyday I learn something new that I hadn't planned for the day before.

Thanks for all your help.