> Just curious. I love VFP but for me anyway, our corporate strategy is to move away from Foxpro and doing most rewrites in VB/ASP/SQL Server (ya, what else is new). I still use VFP for text parsing and other utility stuff but not for any new projects.

> I know most of us explored n-tier architecture with VFP and many of us have done client/server type apps but I have a feeling great many of us are using it for typical file server based apps where VFP still shines best. Am I wrong in my assessment?

In a previous job we used VFP, just as it came out, for a very big, very complex decision support system that is sold as a product. It was the only platform that could handle the complex data crunching we needed while being distributed to customers who couldn't be expected to support a client-server architecture they might not already have in place. We benchmarked the VFP performance against SQL Server, with impressive results. We benchmarked the UI + data access of VFP against PowerBuilder + SQL Server and VFP blew PB away by orders of magnitude.

Currently, I am using VFP to build a small scale application for very small non-profit organizations. Once again, speed, versatility, and my own knowledge base are the keys. However, since there's a possibility I may want/need to swap out the VFP UI or database for something else in the future, I am building this app in 3-tier. (Gee, this is starting to sound familiar...it's in the middle tier that I'm getting the best of VFP).

I've also used it for complex/one time data conversions and ad hoc reporting where I pulled data from multiple data sources (Oracel in Unix, SQL Server on NT, native VFP), sometimes all at once.

(I once worked with a devoted C++ programmer who, after spending about 3 months with VFP, said "This is amazing. You can do ANYTHING with it.")

Isabel