Re: Weird problem a customer is having with a file

James,

Regardless of how the bad data got into the table, I think QuestView should 
fail gracefully rather than crashing.

Perhaps QuestView should display the hexadecimal value of the bad data.

Peter Lunde.

============================================================
From: "James H H Lampert" <jamesl@xxxxxxxxxxx>
Date: 2006/04/20 Thu PM 12:51:35 EST
To: MI400@xxxxxxxxxxxx
Subject: [MI400] Weird problem a customer is having with a file

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
_______________________________________________
This is the MI Programming on the AS400 / iSeries (MI400) mailing list
To post a message email: MI400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/mi400
or email: MI400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/mi400.
============================================================