I am concerned with how best to manage a set of components on the palette.
The issue is in keeping things in sync among a group of developers, and in
how to most easily install a group of components on a new machine. Surely
there must be something less painful than individually installing the same
components on machine after machine?

In older versions of Delphi, I know there was a switch to save a dpr file
for the library, but in D5, I haven't found such a thing.

Bill

Look at the help topic "Sharing objects in a team environment".
Peter Below (TeamB)  100113.1...@compuserve.com)
No e-mail responses, please, unless explicitly requested!

"Peter Below (TeamB)" <100113.1...@compuXXserve.com> wrote in message
news:VA.00005783.00381434@antispam.compuserve.com...

Thanks, but what I'm lookuing for is simplified maintenance of items on the
component palette, not an object repository. Unless I'm overlooking
something here...

Bill

The solution we have come up with is to install third party components to
the component palette only when necessary.   If you do not need to visually
drop them on a form, then don't install them, just add the path to their
dcu's or pas files into your Environment Search path and create them
dynamically.  Then to update them, simply use your version control software
to update each developer and you won't have to re-install the library.
If you have to drop from the component palette, then the only way is to
re-install the components on every station for every update.  I agree 100%
that there should be an easier way.
BrianM.

news:397ca5bf$1_1@dnews...

Thanks, Brian. I'm still hoping for a better answer. It was so much simpler
when you could transport a folder of components, a dpr and fhe complib
file....

Bill