http://www.microsoft.com/vfoxpro/prodinfo/background/newcntry.htmThe above site details a migration path from FoxPro to a Win 32 platform. It is geared to the manager considering whether to stick with VFP or move on to another development tool. Although the end result seems to suggest that you stick with what you know, I find the following fourth option interesting:
// quote
Start over with Visual Basic and the Microsoft Visual Studio tool family (leaving FoxPro altogether in the process)
Microsoft’s Visual Basic and Visual Studio make a leading tool set in the new application development arena. This will entail rewriting FoxPro 2.x applications, but FoxPro 2.x developers will probably find Visual Studio products familiar and easy to learn.
For organizations ready to move to an advanced visual family of tools. This represents an attractive option, providing a leading family of tools from a vendor the organization already knows.
// end quote
Hello!?! Isn't VFP a member of that "advanced visual family"? MS should NOT have posted this contradictory study to the VFP site. In my opinion, that one snippet indicates the general perception in the IT community--VB is MS' golden child...
Regards,
Jack Mendenhall
Manager, Information Systems
Reinsurance Management, Inc.
