>Is this really practical with VFP as the front end and data stored on an SQL server?

Sure. As Larry mentions, you have to shift your paradigm a bit in bringing down data sets.

>Presumably this means that the EXE file will be stored on each location's PC.

I would think so. However, what are they really after? Eliminating the servers? or simply consolidating their data in one place. You could conceivably end up putting the main chunk of data upon a central server and house your static data and application upon the existing servers.

>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?

All depends on your applications needs and the data transmission speed. I'm not experienced enough in bandwidth issues or familiar enough with your applications to make any good guess. Some apps may do fine with 1MB others may need 10MB or more. Look at your applications and the amount of data they must bring down. You'll have to start playing with SQL to really do this. And if you can, setup some slower network link where you can test the performance. You'll start to get a feel for your needs then.

>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?

Learning SQL is something you can do. The pain factor has a lot to do with how big your application is and how soon they want things changed over. If your pressed, you might wish to try to find a "mentor" who can either help you along in trouble spots, or better evaluate your situation so you know more about what your getting into.

HTH,
Anthony Letts