× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



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.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

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.