«

Kevin Audleman wrote:
> My stored procedure
> has 14 parameters. The fourth one is state, which I had as a
> varchar(10), but turns out sometimes people were putting in
> "Pennsylvania".

.... which gets us back to the point I was making about validating the
user-supplied data before attempting to use it.

--
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.

> Bob, you're a genius. That's exactly what it was. My stored procedure
> has 14 parameters. The fourth one is state, which I had as a
> varchar(10), but turns out sometimes people were putting in
> "Pennsylvania".

Well, why isn't state a CHAR(2), and constrained in some way? I wonder how
much bad data has made it into your table?

Bob is completely right: VALIDATE USER INPUT, ALWAYS. And when you can,
take away the opportunity for free text when in reality there is a finite
number of options. Calendar controls and drop-down lists are very easy ways
to avoid the inevitable typo (or intentional abuse).