>>That's why the BEST framework you could use is the one you write yourself. No-one else has a better idea about the specific requirements for you system than you, so you know what you'll need and what you won't.
>>
>>Now granted, to do it right, you'll need an an extensive analysis and design phase. All that will take time, but it's always better to this in the beginning than later, and you're program will be better for it.
>
>Uh, excuse me but I beg to differ. I'm a pretty decent programmer, but I don't think I'm as good as the guys putting out the frameworks. I'd say they all pretty much fall within the top 5% of VFP programmers. If that's the case, then it only makes sense that one purchase one of their packages to make their own apps that much better. I chose F1's Visual FoxExpress, actually started with FoxExpress and now wouldn't think of writing an app without it. I've looked at several of the frameworks, but still feel they are the class of the lot. Plus they offer great support via the web!
>
>John
I have never seen exactly what's in VFE, but tell me, how many of the classes do you actually use and do ALL the problems they attempt to solve apply to your projects.

Take for instance my current project for one of my clients: He wants a MS Office look and feel to his app. Also his requirements are that it's just as important to view the data as it is to edit it. Further he needs reports available to some lists, but not others. We need to be able to switch to a SQL-Server, Oracle, and varuous other 'incompatible' data sources for a back-end without rewriting the logic or the interface. We also need to be able to strip off the front end and turn it into a web style interface to be used on the internet.

Now I certainly am not comfortable relying on the hope that I can adapt someelse's framework for my projects. Maybe you are, but I'm willing to bet there's a lot of overhead on your applications that you don't really need.