01010111
01101000
01101111
00100111
01110011

01010011
01100011
01101111
01101111
01110100
00111111

And also the very first stop to look for answers..seldom disappoints!

So is that the definition for ambition or greed ?!

Search this site for suggestions from some of the members re. version control...here're a couple of links:

link1

link2

Plus...if you'd had the SQL statement in a string variable you could've used the debugging window to print out the sql statement/variables etc.. and run it directly in QA to...

Look up BOL (Books online) - you'll find almost all questions answered there...here's a sampling from BOL..

ntext

Variable-length Unicode data with a maximum length of 230 - 1 (1,073,741,823) characters....

NOTHING is more sacrosanct in our house than watching/playing jeopardy...no matter what anyone's doing, that's one time we're guaranteed to be in front of the tv - the phone is...

Since you say your code is "much abbreviated", it's difficult to see where the error could be...here's the syntax that "should" work...

-- Begin Main procedure --
BEGIN
OPEN get_cases
FETCH NEXT FROM...

just as an fyi - have you gone through all the articles on this site that talk about encryption ?! In case you haven't - here's one on worst...

Just a note - standardized naming conventions also help!

Mehul - please don't cross-post - members on this site monitor all threads...

please respond to this post here

Mehul - please don't cross-post - members on this site monitor all threads...

please respond to this post here

Mehul - please don't cross-post - members on this site monitor all threads...

please respond to this post here

Vladimir - not sure what your objection is towards doing this the conventional way...(with alter procedure...etc.)..

The only other way that I can think of is to directly modify the "encrypted"...

well - a quick update with rtrim should take care of that...