snip<
FWiW: The 0xC is a valid hex sign nibble in Binary Coded Decimal [BCD] which should not ever result [nor ever have resulted] in a decimal data error. To change data from a non-preferred [but valid] sign value, to have the preferred-positive[ed] sign nibble [e.g. 0xF], then any mapping of data into the field will do that. For example, the SQL: update filename set fieldx = fieldx*1 /* FWiW the multiplication by one is probably not required, because the intuitively useless request to assign a field to itself is unlikely to be optimized by the removal of its action */
Regards, Chuck
snip>
It did, however, in 1990 or 1991 when we moved a file from the mainframe to their new AS/400, result in a decimal data error on the 400 (or in some other way make it unreadable.) It was 18 years ago, my memory is not perfect.
Always remember never to say never and always. :>)
Dave B
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
