>>If you have VS on the server use that. Simplest way is to hard code a break in the server code handling the postback ('System.Diagnostics.Debugger.Break()' in C#, just 'STOP' in VB). Of course it's better to do this on a development server rather than the production machine <g>
>
>I don't think I have VS on the server. My question is more about how to return some useful info in the Problems page. Would exception info be available or something along the lines?

Depends. But you don't know whether the page is generated as a result of an exception (.Net or user thrown) or not. TBH trying to maintain a website that has obviously been developed using VS without access to the original tools is always going to be a nightmare. I don't know whether they would work (never used them) but I wonder whether VS Studio Express/Visual Studio Web Developer Express might help?


>
>BTW, I just tried to fill as much info as possible on this form and finally got a thank you letter. So I guess the problem was with some required fields not filled up and the error message was too generic.
>
>Anyway, looks like it works now (thanks a lot to you again), so I may try to concentrate on F C K editor or installing and setting up Subversion.