|
Peter, can you give examples of the invalid data? If there is a discernable pattern in the invalid date values, I'd recommend a WHERE clause to screen those out. For example, if MONTH column has a bad month, say 15. You can screen these types of errors by appending this to your original statement: WHERE MONTH > 0 AND MONTH < 13 or using alternative syntax WHERE MONTH BETWEEN 1 AND 12. Same would go for day and year columns. Hope this helps. -----Original Message----- Thanks, that's perfect! Just one *minor* problem now -- some of the data in these numeric fields do not a valid date make. Besides the usual zero date to indicate no value, there are some that are just plain wrong. I can handle the zero date problem with a CASE clause, but is there a way to trap invalid dates?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.