>>Hi Bret,
>>
>>Yes, this possible. The key is to not make use of local tables directly. Rather, connect to your local tables either through SQL passthrough or through remote views. Instead of using DSN's directly - use a connection object in your database. If your remote views point to a connection - all you have to do is change the connection string of the connection object. Whether your connection goes against one DSN or another is not a big deal. As long as table and field names are constant - you should be in good shape.
>>
>>HTH
>>
>>>Can a VFP application be developed to use an SQL server when networked, but when the exe is distributed use local tables. If this easy to accomplish or is this two separtate developments (network and distributed exe). I have someone here who believes that VFP can be switched SQL/NonSQL at run time. I have no experience with client server so I have never approached VFP but in the DBC/local tables concept. Any suggestions would be appreciated.
>
>John can you define a DSN as you use it above and in you opinion would this direction make the application run slower? The people who are forcing this issue on us are the Network folks, who claim our current operation of having EXEs and data residing on the network, is slowing the network down. They wanted us to investigate an SQL server configuration to alleviate the network slowness.

Brett,

Have you thought of simply moving your exe's to the local drives and pointing at data on the server? This will reduce some traffic (at app startup).