Thinking about it, our choice was to fix the bad data before it is
inserted in the database.
It was possible because the data was inserted from a web page (and we
control the front end application)
If you do not control the application, I would suggest using a trigger to
convert any character below X'40' into space (or a special value).
From: Dan <dan27649@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 03/09/2015 20:51
Subject: Excel Add-in data transfer fails on bad data
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
i Access for Windows v7r1, at latest service level SI56695
I transfer data into Excel and occasionally will attempt to transfer a
record that causes a data conversion error (CWBTF0105). Thus far, it's
been caused by a byte in a character field that has a value of x'00',
x'11', or some other value less than x'20'. This is data from an external
source, so I have no control over it.
Ideally, it would be nice to have the transfer finish completely and add a
2nd worksheet in the spreadsheet that lists all of the errors it
encountered. Since I've seen no indication of such an option, I'm
wondering if there's a conversion setting that defaults a certain
when a non-convertable character is encountered.
This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact