C++ Builder IDE, Howto restrain library path from getting too long?

We have a fairly large project with dozens of forms.
Most of the forms belong to different components, and
therefore reside in different directories.

Recently - after adding one more form into the project -
we ran into a problem that caused C++ Builder to crash
completely during linking phase of our SW. The crash was
repeatable, and was caused by too long library path
approximately 3000 - 4000 characters). When we removed
one form (and one directory from the library path) from
the project, it compiled just fine.

Is it possible to somehow add forms to a project without
lengthening the library path?

I tried creating a static library that contains a form,
but that library won't link unless the form's directory
is added to the library path in the main project that
contains the library. If the directory is missing in the
library path, I'll just get "[Linker Error] Unable to open
file 'UMYFORM.DFM'".

P.S.: We have applied the C++ Builder update #4,
but to no prevail.

...forgot to say it in the previous post, but we're
using Borland C++ Builder 6.0 Professional.

First, and least important, I install CBuilder in a directory Devtools. So I have an initial base
path of C:\DevTools\CBuilder6
Second, I put all 3rd party libraries and components in C:\Libs\....
Third, subst an S: drive to my Source Code directory.

--
-Michael Gillen

Thanks for good tips, especially the last one.
However, that only postpones the inevitable.

I guess then there's no way to link a dfm-file to a static
library in such a way, that the project using the library
wouldn't have to be aware of the dfm-file's location.

As a matter of fact, these tips will be of no use to us
in most projects, since we use relative paths...

That is unfortunate. I use the subst capability to be compatible across different systems where
the source code is actually on differet drives. I had considered using a different drive for my Lib
directory, but it has not been necessary.

--
-Michael Gillen