I'm looking for advice about going to SQL. We have a manufacturing package written in VFP. The application was first written in Fox 2.6 and moved to VFP - we never went OOP. So the tables are still opened unbuffered and we do a lot of scatter gathers still and don't use a database container. Now my boss wants to put a SQL backend behind the package, but make it an option so you can still have FoxPro tables or a SQL backend. I've the book - Client/Server Application with Visual FoxPro and SQL Server. From what I can tell is there is 4 ways to go SQL. Remote Views, SPT, ADO and a mixture of each. We don't want to rewrite a big chunk of code, because of cost, and we want to get the product out of development in 6 to 9 months, because of sales. So can anyone give out some advice about which way would seem best to start down?

You cannot use scatter-gather commands to operate with SQL Server data. You must rewrite all your application with SQL statements - this is because your boss wants application to work either with VFP native DBF’s or with SQL Server. Most of our applications are done in this way. For your regret you should do exactly this – rewrite all application keeping only User Interface and data-model.
I can give you only one advice your boss to outsource this project in outsourcing center like my firm (which will be cheaper for you), where 10 programmers will convert it in a quarter and after that you and your colleagues will continue to support and improve it.