>>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!

This all fits. When you write a commercial framework, you must take everything into account, and think of an army of programmers who will use it. When you write it yourself, you don't have to think about just everything possible, only the things you really need. Kind of similar to the difference between global and local weather forecast. It's also parallel in support: local guy is always close enough to receive a kick in the commandbutt if he's done somwthing wrong (specially if you're the same guy who uses it and writes it).