DataSet Updates fails when there are non-printable characters in a field

  • Thread starter Thread starter Andy Johansson
  • Start date Start date
A

Andy Johansson

Hi

When I try to update my changes found in a dataset I often
get


Concurrency violation: the UpdateCommand affected 0 records.

Because one of the fields (varchar) contains a single TAB chr(9) or
a single CRLF pair of characters.

How can I fail-safe my update code so that even these characters
can get updated?

I guess it is because of the tests that the command-builder
object creates that doesn't like non-printable characters.
Perhaps they should be escaped properly? but how can I do that?

It is frustrating moving to ADO.NET from ADO finding that now
updates fails because there's some odd content in the fields!

Any ideas for simple solution?

//Andy
 
Hi Andy,

Just a thought - did you try using the trim() function - eg,
xvar = trim(irow("fname"))

HTH,

Bernie Yaeger
 
Back
Top