Re: Copying and Pasting from MS Word

On 4/18/11 7:34 AM, rob@xxxxxxxxx wrote:

Redefine the file using SQL instead of using DDS. You cannot get
decimal data errors injected into the file then. <<SNIP>>

Is that not an effective equivalent of "taking a baseball bat to the
person's knees"; i.e. as with contrasting the use of a trigger and use of a CHECK CONSTRAINT, to correct instead of validate the input? ;-)
http://archive.midrange.com/midrange-l/201104/msg00297.html
He-heh... OK, I purposely omitted\snipped from the quoted text, the follow-up questions on how the application does or must respond to the error. :-) And just as alluded in the archived message, the issue will not be just this one application program, but all programs that might have similarly "crappy code" for failed assumptions about what specific error condition transpired; an issue I generally ignore\overlook, because poorly programmed applications are just that, so I see little value in adding "so if your applications are poorly written...". :-)

Seriously though, should not the data at the display file be validated and sanity\bounds-checked versus depending solely on the database for validity checking? Is all RTF data [or whatever is pasted] going to be obviously bad decimal data when input to numeric fields, or might the data be valid decimal yet still be incorrect? And what about character data fields [beyond decimal fields] for which the database will not detect and issue any mapping errors? While the validation or correction of the field data could be pushed down to the database level [to constraints or triggers], depending solely on the numeric validation provided by the database level for the SQL TABLE might be a little weak for the given\subject scenario.?

Regards, Chuck