Hi!

In addition to what already said:

Yes, better learn at least basics of the SQL Server administration and programming of the queries and triggers/SP. This will help you a lot. Simple book by about $40 will be enough, for problems you always can ask here or at opther forum ;)

Yes, Larry is right about the local server at each worksation. There is an option to use MSDE at each local workstation - the lighter version of SQL Server. This will allow you to have most data at each workstation to do not transfer much of data, as well as you can replicate data from/to main server on a nightly basis to keep all data in synch. Well, this is probably similar to what you have now, but you can always do a query to the main server in case certain information required to be as late as possible, in other words, work with 2 servers - local for most data and remote - for certain tables for the most recent data only.

Usually in most cases move to SQL Server require major change of the applications if not complete rebuild, if application for VFP backend was not planned and developed with prediction to move to SQL Server in the future. See http://fox.wikis.com/wc.dll?Wiki~MissionImpossible~VFP, there is an interesting page on this topic.

>I have a VFP medical application which runs happily enough in about 10 locations in London, each location having its own version of the system on their local servers. The headquarters for these 10 locations is now making noises about combining all ten systems into one with the data stored on a SQL server at the headquarters and each location accessing the data via a VFP front end - thus removing the need for servers at each location.
>
>Is this really practical with VFP as the front end and data stored on an SQL server?
>
>Presumably this means that the EXE file will be stored on each location's PC.
>
>Will this result in a significant increase in accessing data provided of course the links between the SQL Server and each location are up to it?
>
>What should be the minimum data transmission speed between the SQL server and each location?
>
>Obviously if I go ahead with this I am going to have to teach myself SQL Server and how to store data in it. Is this a pain or is it fairly easy for the average
>programmer?
>
>I would appreciate any feedback from anyone with experience of the above.
>
>Many thanks
>
>Bob McGilvray