From: "Paul Ranson" 

This is a multi-part message in MIME format.

------=_NextPart_000_0071_01C4852E.B3845300
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Can you not comment out all but one file and see what happens to the = error report?

Paul
  "Gregg N"  wrote in message =
news:4122567c$1{at}w3.nls.net...
  The mssing '>' was only in the post, not in the actual code; I just =
quickly typed in a dummy example.

  I already discovered that the line number is generally correct. What I =
wanted to know is whether there is a way to determine which file. It =
sounds like you are saying there is no way other than examining each = one.
This wouldn't be so bad if I had been modifying only one of the = files.
Unfortunately, I had been working on all of them, and there are = actually
ten of them.

  Gregg

------=_NextPart_000_0071_01C4852E.B3845300
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








Can you not comment out all but one file and see =
what happens=20
to the error report?
 
Paul

  "Gregg N" <greggn{at}invalid.invalid>">mailto:greggn{at}invalid.invalid">greggn{at}invalid.invalid>
=
wrote in=20
  message news:4122567c$1{at}w3.nls.net...
  The mssing '>' was
only in the =
post, not in=20
  the actual code; I just quickly typed in a dummy example.
   
  I already discovered that the line =
number is=20
  generally correct. What I wanted to know is whether there is a way to=20
  determine which file. It sounds like you are saying there is no =
way other=20
  than examining each one. This wouldn't be so bad if I had been =
modifying only=20
  one of the files. Unfortunately, I had been working on all of them, =
and there=20
  are actually ten of them.
   
  Gregg
   

------=_NextPart_000_0071_01C4852E.B3845300--

--- BBBS/NT v4.01 Flag-5