I have resubmitted this problem as it only received one response, which
did not solve the problem. This is an intermittent problem, but occurs
frequently. Please help if you can, or request more details if they
would be helpful.

I continuously have trouble with the Linker
(I have version 3.0). To start with, I have a project that is compiling
and linking fine. I can edit the various units and forms, recompile,
link, execute, etc. with no troubles at all.

However, when I add a new unit to the project (File->New Unit), make
some edits to the new unit, then save (File->Save All or File->Save
As...) the file (with a new name), the linker {*word*99}s out the very next
time I perform a Make ! The error messages are:

[LinkerWarning] Unable to perform incremental link - performing full
link....
[LinkerError] Unable to open file 'COW32.OBJ'
[LinkerError] Unable to open file 'VCLX35.BPI'
[LinkerError] Unable to open file 'VCL35.BPI'
[LinkerError] Unable to open file 'VCLDBX35.BPI'
... <same message, for about 20 other packages>

To recover from this I've been performing the following steps:

(0) delete all the project files from the folder except the C++ source
code/headers (.cpp, .h) and any associated forms (.dfm)

(1) create a new project (application) and save it in the existing
project folder (with the .cpp, .h, and .dfm files)
(2) add all the existing components to the project
(3) perform a Make

This process seems to work fine, and the result is the new project has
the new units added. I suspect that the process above must be avoiding
performing a full link (?) and that the trouble only arises when I add a

new component and a full link is performed (?). But why is the full link

confused about where to get all the BCB packages???

This problem is very consistent and repeatable, and happens every time I

add a new component to an existing project.

Please advise-

Thanks for your wisdom ;-)
--
==================================================
| Tim S. Haynes, Ph.D.
| email: thay...@sprintmail.com
| web: http://home.sprintmail.com/~thaynes/
=================================================

On Mon, 24 Jan 2000 21:22:21 -0800, Tim Haynes <thay...@sprintmail.com>
wrote:

I am unfamiliar with this problem, as I have never seen it.  However, do you
really have to start with a new project?  How about removing all
intermediate state files generated by the compiler and linker?  This should
then allow you to do a "build-all" which is less time expensive than
creating a new project.

Happy Building!
Jody
http://www.hagins.com

: Tim Haynes <thay...@sprintmail.com> wrote:

What did the response say?

BTW, it is not very kind to directly address people directly in the
subject line. I, for one, am rather inclined *NOT* to reply to postings
which directly address TeamB or someone else. Perhaps some food for
thought.

--
General information:
  * Post to the right group - http://www.borland.com/newsgroups/
    * Do not cross- or multipost
      * Research at http://www.mers.com/searchsite.html

Stefan Hoffmeister - http://www.econos.de/
TeamB - http://www.teamb.com/

Hi Jody -

Thanks for the suggestion. I tried that approach except I performed a "make"
rather than a "build-all". I'll try your suggestion the next time this occurs.
Another user mentioned having this same problem in response to my earlier
posting in this newsgroup, but was able to overcome it and eventually purchased
BCB 4.0 where the problem went away.

Thanks for your help :-)

Tim

--
==================================================
| Tim S. Haynes, Ph.D.
| email: thay...@sprintmail.com
| web: http://home.sprintmail.com/~thaynes/
=================================================

response from thread posted earlier in this newsgroup:

I recall having that problem with BCB 3.  After you add a unit, do a BUILD
rather than a make.  When that didn't work, I usually got out of trouble by

deleting the files you mentioned, and also switching the project from "use
RTL" to "don't use RTL" or vice versa.   (Probably was just a superstitious

ritual, but seemed to work!)

Your best bet, though, is to get BCB 4.0.  Much nicer.

I have not heard of this before. What's the deal with this? Who's feelings
have I hurt? Hey - I posted the same message earlier with no particular
group mentioned in the subject line, received a response which I tried,
thanked the person for the input, but still encounter the problem. I
noticed the "TeamB" support and read about them at the Borland web site. It
seemed logical to me to solicit TeamB's help with this problem and this
newsgroup is clearly the forum for that.

Futhermore, your tone in the above passage is itself not very kind. I have
seen many many postings by you offering help in this newsgroup, so I'm sure
your a helpful member of TeamB, but why make me feel like I've picked up
the wrong fork at a formal dinner ;-)

--
==================================================
| Tim S. Haynes, Ph.D.
| email: thay...@sprintmail.com
| web: http://home.sprintmail.com/~thaynes/
=================================================

: Tim Haynes <thay...@sprintmail.com> wrote:

  http://search.yahoo.com/bin/search?p=netiquette

--
General information:
  * Post to the right group - http://www.borland.com/newsgroups/
    * Do not cross- or multipost
      * Research at http://www.mers.com/searchsite.html

Stefan Hoffmeister - http://www.econos.de/
TeamB - http://www.teamb.com/