I'd say you are right if that existing application is already written and there is not intention/need to rewrite it.

I am writing new apps all the time so having the rich and robust environment to get a new app up and running quickly and not have to reinvent things just makes good business sense and it a lot more fun. (it also makes me a lot more money - not that that matters < s >)

I use VFE for this quite successfully. I have, however, done a couple of mentoring project for developers in the situation you describe and trying to retrofit their application - which had often "just grown" without a lot of design or has been just ported over from 2.6 somehow - would have been foolish.

In one case I pointed out they were rearranging decks chairs on the Titanic and given the RAD possibilities of VFE they opted to redesign and rewrite in VFE

In another case it was decided it made more sense to use things like the FFC classes, OCX controls, and tools like Cetin Basoz's excellent Foxy Classes to add functionality.



>I didnt see a category for Frameworks in general so I'll just ask it here.
>I have always had this concept in my mind that frameworks are intended to be a way to help rapidly create an application with rich functionallity and thus the developers who benefit the most from it are those who create new applications as opposed to the ones who spend all there time maintaining/modifying existing applications.
>
>To what degree am I right or wrong in my understanding?