I have never seen this problem. Here are a couple thoughts.
Try changing the SQL field from ntext to text. ntext is for Unicode data and text is for ANSI data.
Another thought (again speculation): your source text may be Unicode and your Remedy ODBC 4.5 driver may not understand Unicode. Unicode puts a null before the standard Ansi characters.
Russel Loski, MCSD
Russel Loski, MCSE Business Intelligence, Data Platform