Now we're getting somewhere. Before proceeding any further, I want to verify
that this is a server-side error, not client-side. In my experience, "line
0" errors are usually client-side errors. Can you confirm one way or the
other? Server-side errors are written to the browser window and always
indicate the name of the page that produced the error. Client-side errors
either produce a dialog box, or an error message in the status bar on which
you can double-click to see details. Which is it?
In any event, your proper course of action is Debugging 101. Either :
a. Eliminate the includes one-at-a-time until the error disappears
b. Create a new page and add the includes in one-at-a-time until the error
appears
That should allow ou to identify the problematic script.
Bob Barrows
Adam Short wrote:
It points to a file which links a load of include files, it could be
any one of a dozen include files.
I can't get my head around line 0, as far as I know all line
numbering start at 1!
I've decided to shut the server down tonight and run a complete scan
disk and defrag
"Bob Barrows [MVP]" <re******@NOyahoo.SPAMcom> wrote in message
news:e9**************@tk2msftngp13.phx.gbl... Adam Short wrote: If I knew which script page was causing it!!!
I still can't comprehend why you don't know which page is causing
this error. The error message was copied from the browser window
wasn't it? What was the url in the address bar when te error
occurred?
Bob Barrows
--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so
I don't check it very often. If you must reply off-line, then remove
the "NO SPAM"
--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.