>Hello,
>
>In his (very good) book "Advanced OOP for VFP" Marcus Egger preaches that the best reuse of classes would be to share them over all your applications. We find this a nice idea but practically impossible to execute because you would influence all your projects by each change of a class (also those apps you do not want to touch anymore). We ourselves copy our framework with all subdirectories, classes and files into a new separate directory at the start of each new project.
>Is there anybody who has some more ideas on this ?
>
>Thanks,
>
>Koos.

Here's what I do:
- Parent class level. This is a subclass of the VFP base classes with very little change

- Framework level classes. Subclass of Parent level. More functionality added.

- Utility classes. Subclass of Framework classes. This actually adds to the framework and has things such as file pickers, specialized textboxes, etc.

- Customer level. Subclasses of Framework and Utility. This is subclassed for each customer.

- Application level classes. Subclasses of customer level.

I've redesigned things about three times before I got to this level. One thing I used to do was have all the data "navigation" code in the form. Things like Save, Go Next, Find, etc. I've now broken this out into a custom class that I can drop on any form. This also makes it easy to change the data source from DBF to SQL to ADO, etc.