Peter Lunde <lunde@xxxxxxxxxxxx> wrote:
Regardless of how the bad data got into the table, I think QuestView should fail gracefully rather than crashing.
Uh, yes, that's the general goal here, and that's why I'm on the MI list about it.
QuestView deals with an awful lot of different "problem I/O" situations, including data mapping errors on writes, and the ever-popular decimal data error.
At this point, however, I'm not even entirely sure what I'm looking at. Maybe sometime today I'll be able to see whether or not the bad data even makes it into the buffer.
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.