However, no matter what conversion route you choose, the conversion will run your existing application AS IS, in the new Visual FoxPro environment. The second question directly affects the first of Visually or Functionally converting your screens. Secondly, decisions have be made on how you wish to incorporate the new extensions found in Visual FoxPro. First, it must be decided if you want to take the default Functional conversion, that completely converts the 2.6 screen to a backwardly compatible Visual FoxPro form set, or Visually converting the form, which entails running the 2.6 coded SPR and manually implementing the converted form set. Successful conversion of an application requires planning of how the components of the application will be converted. With this conversion you can start using these wonderful new features while still leveraging your existing development investment. This paper will look at how you go about converting your existing 2.6 application in Visual FoxPro. The expansiveness of the new FoxPro features can be daunting, but this is mitigated by the conversion utilities built into VFP. Even though Visual FoxPro’s new environment provides a whole new way of doing things, your existing FoxPro 2.6 application can be almost seamlessly integrated into this brave new developer environment.

From object orientation to visual form and class tools, the whole application scheme has been revamped.

Visual FoxPro 3.0 has opened up a wealth of new developer tools that can only be considered as revolutionary for the FoxPro programmer. Converting Your Existing Applications to Visual FoxPro 3.0

Foxpro 2.6 multiline buttons