>>The question really is, should you get someone elses framework, or build your own. If you don't purchase a framework, you end up doing something similar by yourself.
>
>Well there is another question. I have talked to peaople at big project shops that use frameworks. When a VFP framework project gets in trouble - and that can happen a lot because somehow these shops would rather substitute a framework for skilled software designers and skilled software developers. And when the customer starts to gripe - the project gets in trouble - it's not the low-skill hiring practices of the "framework" shop or the "framework" that gets blamed. No - instead it's blamed on design flaws in VFP.
>
>I don't mind frameworks. But if you use a framework - use one without fox in the name - and don't tell your clients you're doing it with VFP - dad-nab-it!:-)

I small shop client I once had, requested a simple inventory system. When I suggested VFP, he frown. I then ask if C++ would be more to his liken, and answered "Well, Yes". I then noted to him that VFP is written in C++. And he responded with an "Oh, Ok".

Another time, I built a medical software in VFP 6.0, but told the clients that it was written in Visual Studio (well it did have a COM object written in VB).