>> I have designed my own, quite efficient and robust application framework...
>> I was just wondering how all you folks in the VFP community have been
>> dealing with using the same framework for different applications...do you
>> use a wizard to create a new project? Copy the framework to your new
>> project directory? Or just reference the same set of VCX's and PRGs for
>> all your apps?? We're deadly curious!
>
>I have a 'System' set of visual classes that define behaviour for all
>objects, some objects created in code, a Debug menu, a Startup
>application, etc. This exists once on my computer, and is used in every
>application that I write. This includes the Forms handler, the DE
>manager, the error handling code, etc.
>
>Then for each customer, I ahev a set of files that are subclassed from
>the 'System' set; then for each project is another level. The reason to
>have two levels (one at the customer level and one per project) is
>simple laziness. If the customer changes a logo, has a standard set of
>business rules, or whatever, then I only have to change things once.
>
>The 'System' level code remains copyright me, and if I use it in a
>customer project then they get a copy of it and a license to use it, but
>they get no right to modify it or claim ownership. If they want to
>claim ownership of the code, then I ignore the canned libraries and
>start from scratch. They ultimately pay more, but they get 100%
>ownership, instead of something less than that. It seems to work well.
>
>/Paul

Laziness?? Nonsense. That's a great idea! That's exactly the power of OOP!

Paul, I love the way you implement that.