Tracy;

The requirements for applications differ. Some are conversions, while others may be built from the ground up. Lots of other possibilities exist.

I had a major VFP project that someone began two years previous to my being called. Four people worked on it and it had problems. I took my own foundation library, blew away all code, and changed classes to my own (with a tool I developed for the purpose). It worked seamlessly and got me a nice big contract to boot! I did not change the UI at all.

To have the functionality of a framework you have to replace all foundation classes with your own or one from a third party. That requires you know the foundation well. This may or may not be practical.

From another viewpoint, integrating an existing framework with your own framework can be simple – again understand both frameworks.

After working with products like VFE and VMP, when I work alone, VMP was best for me. It took less time to do what had to be done and has a style that lends itself to how I like to work. With a team VFE had advantages if you dedicated someone to each task - create and modify classes, etc. The idea is to be productive, understand what you are doing (do not screw up the framework) and enjoy yourself! :)

Another point I use VSS regardless of if I work alone or with a team.

Tom


>A pre-existing VFP application built entirely in VFP with no framework or third party components at all. Typically, frameworks are used entirely for new development or in other words, all new apps created from scratch. There is typically no way to bring any of the classes/controls from a framework into an existing app and have them function correctly without the underlying framework dependencies bomb. I was hoping one of the frameworks out there allowed this.
>
>
>
>
>>What do you meant "vanilla Visual FoxPro app"?