>Another point is that once U have developed a
>template for one client, U can reuse the code base
>for other clients. Hopefully, this original code
>base will continue to be tested each time U use it
>for a new client and improve over time. That's my
>strategy.

What level of reuse are you expecting?
What level of reuse do you get?

I think reuse decreases the further down your hierarchy you get
from the VFP base classes.

Framework code has to be generic, not related to any particular application - but it will to some extent force you to adopt a style of interface or user interaction that not all customers may want.
You might have two frameworks or even more, depending on what kind of application you are building.

Application specific code probably cannot be reused without taking the time to make it more generic - not something you do when you're up against a deadline.

Customer specific code won't be reused at all.


I can see this approach will work as long as the clients are in the same business, or they want the same user interface.
Or you settle for a generic template that doesn't achieve much beyond coordinating toolbars, menus, and forms managing 1-M or 1-M-M relations.