Ken Dibble wrote: >> I've checked the values in the Transdate column in that table: 1 record >> with a crazy date back in the year 0120, 2 records where it was 0220, 1 >>from 1901 and the rest appear to be normal. And these goofy records >> aren't even the ones in the query result. > > I don't know the answer to your problem but the above got my attention. > I've got a handful of records in a table of about 30,000 service dates > where the year is something impossible like that: 0007, 0008. I don't see > how this can happen. SET CENTURY is ON, and the textbox where the dates are > entered is formatted for dates, so if a user entered a date like 10/1/0007 > s/he'd get a VFP Invalid Date error and wouldn't be able to do anything > until s/he fixed it, let alone saving the data. Also, my date validation > code won't allow service dates to be entered that are more than a couple > years old. Again, this has only happened with about a half dozen records > out of around 30,000, so it has to be something extremely random. > > I wonder if you have any thoughts on how such years can get entered?
In my case, these dates could have been entered long ago, as this app is very old (but still kicks ass....lol!). Perhaps it was before they put any constraints/controls into play to force "good" dates. _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
