Re: Debug stored procedure in query analyzer

Perhaps the debugger does something to the input, where what it does is dependent on Regional Settings in windows?

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/


"CDuttlinger" <h2oPower@xxxxxxxxxxxxxxxx> wrote in message news:ED00A9CE-A366-4F9D-B60A-7DE5F090302E@xxxxxxxxxxxxxxxx 
That doesn't explain why debug works on some computers and not others, with
the same stored procedures.
--
Carole


"Narayana Vyas Kondreddi" wrote:

You may have to specify date parameter values in a specific format. For
example, see:
http://groups-beta.google.com/group/comp.databases.ms-sqlserver/browse_thread/thread/31e4a338e1b6d5d0/90f1164645c4a4f9?lnk=st&q=Invalid+character+sql+debugger&rnum=2&hl=en#90f1164645c4a4f9
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @ http://vyaskn.tripod.com/



"CDuttlinger" <h2oPower@xxxxxxxxxxxxxxxx> wrote in message
news:6E2C1A97-A747-4BC6-979B-CE090C67B6A4@xxxxxxxxxxxxxxxx
> Trying to use Debug feature in query analyzer -- on some systems I get the
> message
>
> [Microsoft][ODBC SQL Server Driver]Invalid character value for cast
> specification
>
> There's nothing wrong with the stored procedure. If I have this problem,
> it
> happens with all stored procedures except those that have no parameters.
> If
> there are no parameters, the message doesn't show, but debug still doesn't
> work properly.
>
> -- > Carole




.

Relevant Pages