>Seperate prgs huh? Gotta love it when the simple (but effective) is not so obvious. I'm with you on the issue of having to carry around a lot of baggage porting proc files from one app to another when most of the functionality is not needed. I'm going to go to your model for my own development. One disadvantage though would be administration on a large system with a larger development team. Unless you're working with folks who document and administrate well, it would be a nightmare trying to keep track of prg functionality and which ones ship with what app. It definitely wouldn't work in the shop I'm in (sad to say). Thanks for the tip. You just changed the way I think about prgs.

Jim,

Just put all of those prgs in one directory. Write code that calls them and build the project. The PM will go out and find (or ask you to) the prgs it needs and include them in the project.