# 3875 CASTing Strings as Memo Types Can Cause Extra Null Terminator at End of String

---

I think we’ve stumbled upon a bug that appears to have been introduced into the DBISAM components as of 4.34 build 7. Testing with versions prior to this (up to 4.33) don’t exhibit the problem.

Essentially, when appending text to a memo field via SQL, we’re seeing a null byte (#0) getting appended to the field data too. Interestingly, subsequent appends via SQL keep shifting these accumulating null bytes to the end of the field data. However if data is appended via code using a dataset instance, the new data is appended *after* the null bytes.