Hi,

>>
I am sure, that after finding the answer (if that ever happens!), it must be something you can fit in 3 lines of help text, but the way it is now, you can go forever from one hyper link to another, and learn more and more about less and less, until you will know everything about nothing, and you can call you a specialist.
>>

Some truth in that<s>. It doesn't seem unusual to end up reading 10 pages of documentation to uncover the one line of code you need !

>>
>Your exception should give you a full path which will at least tell you where it was attempting to find the file (probably the system folder)
>
It would be nice, but it doesn't, it says:
An unhandled exception of type 'System.IO.FileNotFoundException' occured in System.Xml.dll.
Additional information: FileNotFoundException
>>

FWIW, as a quick test, I forced the same error in a web service. With error reporting enabled on the browser the error was:

System.IO.FileNotFoundException: Could not find file "C:\WINNT\System32\myFile.xml"

If I put the XML file in the specified folder it did indeed find it OK - but that's not much of a solution - wouldn't want files like that cluttering up the system folder. It does however suggest that .NET is searching some form of path list, not finding the file, and, perhaps just throwing up the system folder in the exception because it was the first (or last) in the path list ?? Not much help really....

Regards,
Viv