> "If I wrote an app in VB 6.0, can it be moved?" Green asked. "If it works, maybe I shouldn't try."



Rick;

I take this statement to mean if a present application in VB 6 does not work you should try to "move it". Sounds like the questions about converting FoxPro 2.x to VFP. If you want a maintenance nightmare go ahead and do it. It takes time to learn any new syntex, language or programming concept. The investment is well worth the return if you do it at the begining and not when the application is completed.

Would we want to use FoxPro 2.x concepts for Visual FoxPro? Not me baby - I love OOP and VFP. The old way has too many limitations. I remember when VFP was being introduced it was stated that perhaps 75% of the FoxPro developers would not make the grade with Visual FoxPro. Seems about right if I look for the faces I once knew who are no longer a part of our development community. The same thing might happen with the Visual Basic developers or they will stay with VB 6, with his/her head in the sand.

Not everyone has to do the latest - greatest from Microsoft. There are a number of people out there making a living taking care of FoxPro 2.0 DOS applications. They may not be rich but they might be happy.

It may be two or three years before .NET is in wide use by the development community. I am sure it will take more than one Service Pack to get the kinks out.

Tom