>We are about to take a major VFP application to SQL7 and are undecided on the front end. Some in our shop say that VB, as a front end, has a more robust set of tools/controls for handling large data sets in SQL7, since Redmond designed it that way. On the other hand, the shop has a much stronger skill set in VFP. We would be interested in all arguments for either.

I too have undertaken learning VB, just to hedge my bets. However, I am firmly rooted in VFP and until something better comes along, that's where I'll be.
I have just been hired as a consultant for a project with Ingram-Micro. While looking at the project, they told me how they had built this system using VFP as a front end to SQL Server 6.5 (subsequently moved to 7.0) as a temporary fix for their "shop floor control" program. The original program was only supposed to be around for 6 weeks, when the "real" Oracle program would be brought up. That was last year. Ingram-Micro has now decided to scrap the Oracle system and install the VFP/SQL Server system in all their plants.

This program basically runs the entire plant and controls what parts are used in every conceivable computer configuration. There's no telling how much money they are going to save by using VFP and SQL Server instead of Oracle. I plan to talk to the chief architect of the system about entering it in the excellence awards for next years devcon.

I've seen FoxPro kick butt so many times against mainframe apps, other desktops, etc. I'm sure most of us can relate. As for choosing VFP as the front end, they love having the speed and flexibility VFP offers, and so do I. Longer term, we are talking about making it a web based application using Rick Strahl's Web Connection.