String legnth too long???

sithlrd · May 9th, 2005, 02:14 PM

I have a Stored proc that has a â@cityList varchar(2000) = nullâ as an input parm.

It is querying a table thus:
            Declare @SQL varchar(1000)

            SELECT @SQL = âSELECT producerID, ProducerName from tblProducers where City IN (â + cityList +â)â

            Exec (@SQL)

All is well and good if I pass in ââMontgomeryâ, âBirminghamâ, âAtlantaââ. However, if I try to pass in a string with more than 128 characters, it gives me âThe identifier that starts with <LONG STRING CUT OUT> is too long. Maximum length is 128.â

Is there any way to pass in my cityList if it's greater than 128 characters?

om_prakash · May 10th, 2005, 10:51 PM

Please change the double quotes to single quotes. I think u are using double quotes when passing parameters to this SP.

Om Prakash

sithlrd · May 11th, 2005, 07:25 AM

thanks for the reply, I was starting to loose hope. :)

Actually, I'm passing the parms like this:

Quote:

quote:command.CommandType = CommandType.StoredProcedure;

Quote:

command.CommandText = "spGetPickListProducers";

command.Parameters.Add("@cityList", SqlDbType.VarChar,2000);
command.Parameters["@cityList"].Value = cityParm.ToString();

con.Open();

SqlDataReader reader = command.ExecuteReader();

Prashant.k.m · May 12th, 2005, 07:07 AM

hi,

First of all see the lines

Quote:

quote:
"@cityList varchar(2000) = nullâ as an input parm.

It is querying a table thus:
Declare @SQL varchar(1000)

@cityList is 2000
@SQL is 1000 -> make it 4000

Fix It first

Prashant

sithlrd · May 12th, 2005, 07:13 AM

Already done, actually. Result is the same.

sithlrd · May 24th, 2005, 08:47 AM

Any other suggestions?

sithlrd · September 24th, 2013, 04:16 PM

Finally got around to refactoring this app... 8 years later, my kids are driving age and I'm still coding. LOL... it's now done in LINQ with like 5 lines.