Re: CPF5035 used to be ignored, now causes SQL to fail

[BMay@xxxxxxxxx]

Agreed.  You would definitely want to fix the actual problem.  Just 
proposing a stopgap in the meantime.

Brian May
Project Lead
Management Information Systems
Garan, Incorporated
Starkville, Mississippi



Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
01/20/2011 07:00 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc

Subject
Re: CPF5035 used to be ignored, now causes SQL to fail






On 1/19/2011 4:07 PM, BMay@xxxxxxxxx wrote:
> Just thinking out loud, but would a BEFORE INSERT trigger allow you to
> examine the buffer and make corrections before the 406 error occurred?
Yes, that would probably be an option.  But the better option is to fix 
the file when necessary and then fix the program that writes to the file.