From: Groleau+news@FreeShell.org   
      
   On 03-09-2011 14:16, Gert-Jan Strik wrote:   
   > I don't know much about SSRS.   
   >   
   > Having said that, you should at least double check that the column   
   > Description is really declared as varchar(50), and not accidentally as   
   > varchar(1) (which you would get if your original create script used the   
   > datatype "varchar").   
      
   Yes, it is.  I checked all details and foud them all as they should be.   
   All details except ONE:   
      
   Don't know how this happened, but "something" had converted the   
   original text in the table to UTF-16, and inserted it back into   
   the table as if it were ASCII, making every other character a null.   
      
   SSRS was attempting to render what was actually there as the datatype it   
   was claimed to be.   
      
   Since I had seen the correct text in the table shortly before seeing the   
   bogus text in SSRS, I didn't bother looking there again.  A colleague   
   actually found it.   
      
   This reveals two bugs though: SSRS did the right thing in a text box,   
   showing each null as a "box."   But in the _menu_, it treated the first   
   null as the end of the string.  And SSMS did the same thing in the   
   results grid of a select.   
      
   --   
   Wes Groleau   
      
      Hail that dog!   
      http://Ideas.Lang-Learn.us/BlindDog?itemid=4020   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)