[EMAIL PROTECTED] wrote on 06/09/2006 10:16:08 AM: > >SELECT TESTFILE WITH DATE > 14000 > Bad data "14000" for conversion "D2/". Unconverted data used for > selection. > > 8 record(s) selected to SELECT list #0. > > > CLEARSELECT > > >SELECT TESTFILE WITH DATE > 14001 > > 0 record(s) selected to SELECT list #0. > > >SELECT TESTFILE WITH DATE > 14365 > > 0 record(s) selected to SELECT list #0. > > >SELECT TESTFILE WITH DATE > 14366 > Bad data "14366" for conversion "D2/". Unconverted data used for > selection. > > 2 record(s) selected to SELECT list #0.
So why are you using internal date values against a date-formatted dictionary item?!? If (for whatever bizarre reason) you want to do that, just use a dict item that specifies a straight numeric value. For the record, this is looking at 14001 as year 14, Julian date 001. 14365 is Julian date 365 in year 14. 14366 is day 366 in year 14. Oh, wait, there was no day 366 in year 14 - bad data. Hey, there was no day zero (14000) either! Make it easier on the humans and unambiguous for the computers. Use external dates. Tim Snyder Consulting I/T Specialist , U2 Professional Services North American Lab Services DB2 Information Management, IBM Software Group 717-545-6403 [EMAIL PROTECTED] ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
