Re: SQL insert error - value for column too long -- 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: SQL insert error - value for column too long
From: Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>
Date: Tue, 28 May 2019 10:36:38 -0500
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@lists.midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.lists.midrange.com>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

On 5/28/2019 10:32 AM, Steve Richter wrote:

I think the DSPFFD is too long to post completely. 64 columns. Both
tables have the same number of columns. The same record length. But
columns are not in the same sequence in the buffer.

I think this is your issue.

If I am reading your post correctly, the columns need to be in the same order.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: SQL insert error - value for column too long , Robert Rogerson

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.