First, I'd strongly recommend using Visual Source Safe. I've used various version of VSS, since 1994 (Borland Pascal, Delphi, etc). As big a pain as it is with VFP, it will save you often enough to make it worthwhile.

We have basically 2 product lines, Beverage & Accounting. As Jim diagrams, we start with BaseClasses that sub-class the VFP classes. There is no code in our BaseClasses. Next we create our WinReuse sub-classes. These controls are written to have no dependencies for either of the product lines. Next we have class libraries that are specific to the product lines, but that can be used in up to 15 or 20 different apps within a product line. Finally, we have class libraries that are specific to each app.

Each type of library is archived in VSS and grouped as Forms, classes, code, reports, other, etc. The only problem with this organization is that getting paths set in the development environment only allows me to have the current app I'm working on in the path. If I need to work on WinReuse or beverage classes, I use the project manager to modify or I have to change the the correct folder structure to add items to the project. We've discussed, but haven't yet implemented, a basic project with all of the currently used items already added to the project.

I strongly recommend that you label certain milestones in VSS, so if you are working on a new feature, you can get to the source code that is labeled so that you can rebuild an older app with the correct code.

HTH