My fellow MI geeks and gurus:One of our customers sent me a physical file that's crashing our QuestView product in a way that's like nothing I've ever seen before. It seems that the file (which appears to have been created in SQL) has a date field, and when we attempt to read the last record in the file, it produces a data mapping error on that date field, apparently because it fails a constraint.
I've heard of date fields producing data mapping errors on write operations, but never on read operations; moreover, I thought that in SQL files, all validation that's built into the file happens on the write, rather than the read.
Any idea what it is I'm looking at? -- JHHL
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.