>> Right. I tested it by surrounding my input with <b> and </b>. To my
>> surprise, it causes an unhandled exception: A potentially dangerous
[quoted text clipped - 9 lines]
> Can you explain a bit more about what is and, more importantly, what is
> not valid data in this case...
>> Can you explain a bit more about what is and, more importantly, what is
>> not valid data in this case...
>
> It's a very simple site (http://www.rentalprofitcalc.com). Visitors enter
> several data fields. I then do a postback to a different page.
Any particular reason that you postback to a different page, AAMOI...?
> That other page examines the fields, performs calculations on some of
> them, and creates a report. Some fields, such as the property and loan
> names, are simply strings that are displayed as is (there is no invalid
> value).
There doesn't appear to be any validation at all - e.g. it's possible to
enter "Hello" in the purchase price... My advice would be to fix that
first...
> BTW, I tried the same thing (<b> and </b> in the property Description
> field) when the app is running online and it still causes an error but
> does not display the details.
Obviously the absolute last thing you want to do in a live site is actually
display an error to the user... Instead, capture the error with proper
exception handling, email yourself the error and all its metadata, redirect
the user to a friendly page where you apologise that something has gone
wrong and, depending on what the error actually was, advise them how to
proceed...

Signature
Mark Rae
ASP.NET MVP
http://www.markrae.net