That's what I was thinking with the SQL statement, but I seem to remember
trying this recently and having the statement simply die when the offending
record was read.

I'll try it again, though.

Thanks.

Donald R. Fisher, III
Project Manager
Heilig-Meyers Furniture Company
(804) 784-7500 ext. 2124
Don.Fisher@HeiligMeyers.com

<clip>
IIRC, I had a situation where a field was messed up and should have been 0.
So I could "UPDATE filename SET fieldname = 0 WHERE (fieldname < 0) OR
(fieldname > 99999)".  This worked because I knew it should not be negative
and it was a 5-digit zoned decimal field, so 99999 was the largest value it
could hold.
<clip>


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.