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

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: CPF5035 used to be ignored, now causes SQL to fail
From: Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>
Date: Thu, 20 Jan 2011 06:51:31 -0600
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

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.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

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

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.