> This is very very very annoying because I cannot remember all the syntax
for
> all the commands, and I cannot remember all the commands.  So I frequently
> use the Code Insight and Tooltip Exression functions.

> My project is now 3286 lines long, and I am getting very wound up by
having
> to jump to a line above line 2879 to type some code (being able to use the
> code insight etc), to then have to select the code i've just typed, cut
it,
> and find the position in my program where I actually want this code to be,
> and paste it in.

> This is driving me absolutely nuts, as I cannot see any reason for it.  It
> only seems happens on this project, i've tried copying the text to another
> file, creating a new .cpp file and re-pasting all the code back to the new
> .cpp file and it still does the same thing.

> Does anybody have any suggestions on this, as I am clean out of ideas, and
> need to get around this major annoyance..................

> T.I.A Woody.

> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.372 / Virus Database: 207 - Release Date: 21/06/02

> > P.S  I'm using BCB5 Enterprise on WinXP, and I think I have Update#1
> > installed (which seems to be the only update).

> I remember this from BCB5 but so far haven't seen it with BCB6. OTOH
> BCB6 can sometimes fail to provide CI information because (and a dialog
> pops up to tell you) 'there are errors in your code'. What's a bit
> silly is that occasionally the error is the line I need CI for. The
> solution is simple enough, remove the line that's under construction
> then compile the unit then restart the line. It's an improvement on
> BCB5 (BCB6 genuinely is despite what some people say here) but still
> not perfect :)

> Andrue Cope
> [Brackley, UK]

> > P.S  I'm using BCB5 Enterprise on WinXP, and I think I have Update#1
> > installed (which seems to be the only update).

> I remember this from BCB5 but so far haven't seen it with BCB6. OTOH
> BCB6 can sometimes fail to provide CI information because (and a dialog
> pops up to tell you) 'there are errors in your code'. What's a bit
> silly is that occasionally the error is the line I need CI for. The
> solution is simple enough, remove the line that's under construction
> then compile the unit then restart the line. It's an improvement on
> BCB5 (BCB6 genuinely is despite what some people say here) but still
> not perfect :)

> Andrue Cope
> [Brackley, UK]