>>Agreed, but have damn practical question: could you imagine VB developer suggesting to use VFP as middle-tier extension of his VB front-end?
>
>Edward,
>
>We can equally ask, "Can you imagine a VFP developer suggesting to use VB for the front end on his VFP middle tier project?"
>
>The issue here is that MS is promoting componentization, that is using different development tools for different parts of a system. There will be developer's who embrace this idea and they will investigate the best tool for each part. There will also be "tool-bigots" who will force their favorite tool to do everything even when that is contrary to the best interests of the client.

Actually, as a VFP programmer I might very well suggest using VB as a front end. VB's controls are real Windows controls. VFP's aren't. You can't use a lot of add-on products that work with VB (and other proucts, like Delphi) because they expect the controls they work with to be windows. I would also recommend VB if there was a chance the customer would ever want to use the application with Windows Terminal Server or Citrix WinFrame. VFP performs poorly with these products while all other Windows apps I've tested work quite well.