>Somebody told the boss that we needed to go client/server (I didn't agree), so he bought SQL Server 6.5 and put me in charge of making it work. As I move my VFP apps over to SQL, I am finding that instead of remote views I use SQLEXEC for nearly everything, either sending SQL statements or calling server stored procedures.
>
>This makes me wonder whether in this situation--100% of our data is on the SQL server--something like VB would produce executable apps that are lighter but just as functional as VFP. I currently use a simple EXE that goes to the server to get VFP apps; there's no substantial code in the EXE. Eventually I would like to use a browser as the front end and forego the EXE entirely. Any advice on how to plan future development? Should I start learning something besides VFP now that I have no native Fox tables?


In addition to what Mark said, the OOP capabilities of VFP also help it to outweigh VB.