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

I am doing both file-based and n-tier applications, using VFP for the middle-tier COM objects.

VFP is extremely well suited for the middle-tier, maybe even more so than VB. Fox people are not the only ones saying this. In Jan, 1999 Software Developer magazine reviewed VFP 6.0 and said "Visual FoxPro 6.0 has developed into a worthy rival to Visual Basic when it comes to building Windows-based client/server and Internet database applications, as well as data-intensive components that you can use in a variety of enterprise scenarios." It then goes on to say "Visual FoxPro 6.0 may have a leg up on the other languages in Visual Studio, particularly when it comes to creating COM components that you can manage and scale with Microsoft Transaction Server." You can read the entire review online at www.sdmagazine.com.