Re: How is it possible to have invalid time in a time field?

[James Lampert <jamesl@xxxxxxxxxxxxxxxxx>]

I haven't been following this thread, but one of the things I had to 
deal with a few years ago in QuestView was that if somebody tries to put 
invalid data into a date, time, or timestamp field, data management 
(called from MI) rejects the write/update operation with a data mapping 
error. So I had to write an awful lot of code just to validate input to 
these field types, and to warn users that they were present, and to keep 
the data mapping errors from crashing the whole application.


Bottom line: even going through the Data Management runtime (rather than 
SQL), there's an awful lot there to keep invalid data out of these 
fields. It seems to me that somehow, something must have gotten into the 
file on a level that can see and manipulate the raw bytes of date, time, 
and timestamp fields.