So, explain the code Gail wrote for you... I wanna make sure you actually learned something other than how to get other people to do your work for you...

Figured the original poster wouldn't have gotten a thing out of it... you know... the "flying pig" thing...

Ooooowwww.... why on Earth do you want to do this?  Even if it's just a report, if someone needs to ananlyze the data using any form of aggragation, they're pretty...

>>i geting problem.

Any chance of you describing what that problem is?  Error message? ????  You might get people to help a bit quicker that way...

Sam,

I don't work with multi-lingual databases so I've no example for you.  However, COLLATE is the answer you are looking for... take a look in Books Online for COLLATE.

This is a very "old" problem and there must be a thousand or so posts on how to do this on this forum alone (search does work)... but, here it...

Not sure, Gail, but I think you just did someone's "urgent" homework for them...

I'm right there with Serqiy... I use system functions whenever I can...

I'll probably get my head handed to me for using undocumented features but I believe this works both...

That also takes care of the problem when unpredictable lengths occur without a hint of a loop.  Nicely done!

Heh... I thought you said "without looping".

Nicely done... If I may suggest, however, a method that avoids both loops and dynamic SQL...

--===== If the test table exists, drop it

     IF OBJECT_ID('TempDB..#HexToAlpha','U') IS NOT...

He doesn't get it as a hex/binary number... he get's it as a string.

Nicely done, Brian.  And, Jan, I agree... we've asked you to post the cursor code a couple of times now...

There is a "good" reason ... they're probably not allowed to put their own stored procedures in and it must pass a DBA review......