|
Oh, and there's also a paradox:1. The "problem" record of the file comes up with a nonzero value in the date field's position in the nullmap, which implies that the field IS null-capable, and
2. QuestView, which can easily null-out any normal null-capable date field, CAN'T null-out the date field in this file, either in existing records or in new ones, which implies that the field ISN'T null capable. This is corroborated by the fact that a DSPFFD on the freshly compiled file says that the date field is null-capable, yet a DSPFFD on the "problem" file says no such thing.
This starts to remind me of a puzzle in the Infocom game version of "The Hitchhiker's Guide to the Galaxy": the "tea and no tea" puzzle. I'm convinced that if we knew what a "2" in the nullmap means, we'd know what's going on here.
Now if I had the slightest idea what a "2" in a nullmap is supposed to mean, I'm convinced that I'd be able to figure out what's going on.
-- JHHL
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
