Martin, I am working mainly to support existing projects, and writing helpers or COM server replacements, so size is an issue, much easier to update a 40K file by asking the payroll clerk to exit than ask the company to shut down so you can update a 6M executable twice a year for tax table changes!

The issue is, do I start to strip out parts of the 6M project into the COM servers, or link back & modify the big library?

I've noticed that the damn project manager seems to find more & more of the big system on every build of the small COM servers, so I am ending up with BOTH, a copy in the main project, and a copy in the COM project!

Moving the methods into stand alone .prg's should solve this, but that means the projects will have half their code locally, and half in a shared area.

by design, I re-use some names to load different programs , it helps with security and makes the system more flexible! ( eg CASE 1 set proc to sales
CASE 2 set proc to support
DO Inquiry )

So I can't just stick everything in one directory!

I think a framework would be too complex for small COM servers, where I don't want a lot of overhead.

thx for the sugestions, though, I will try to test drive the frameworks

mike