At 09:43 AM 31/12/2009, you wrote:

>Have tested this now in a database and found that a chr(0) in the text
>cannot cause this behaviour as it won't then show the bit
>after the chr(0) in either application. In VB this was tested by doing an
>update of a table field with the string:
>
>"123" & chr(0) & "567"
>
>So, there has to be something else going on or it has to be a different
>character to cause the trouble.

1. Considering that you can "see" the whole string in one application and not in another, it can't be seen as "corrupted data". It looks like a difference in the way the respective visual interfaces display the strings. Could it be that the problem data contains linebreak characters, that one application treats as trimmed whitespace, while the other applies the actual linebreak behaviour, meaning it can't display the rest of the string in a single-line control?

2. Have you queried the "offending" records using isql?

./heLen