You can use UNION ALL in a view. Perhaps you could structure your view to
have the two large comments as two separate records in the view?

Create view LIB/TEST as
(select KEY1,COMMENT1 from LIB/FILE
select KEY1,COMMENT2 from LIB/FILE)

m> To
Sent by: "Midrange Systems Technical
midrange-l-bounce Discussion"
s@xxxxxxxxxxxx <midrange-l@xxxxxxxxxxxx>

03/26/2008 11:21 Subject
AM SQL View Problem.. Is there a

Please respond to
Midrange Systems

I am getting the following error (trimmed for content):

SQL State: 54010
Vendor Code: -101
Message: [SQL0101] SQL statement too long or complex. Cause . . . . . :
The SQL statement is longer than the limit allowed for length or
complexity. The reason code is 3. One of the following reason codes
indicates the error: 3 - The sum of the lengths of the non-LOB columns in a
select list, table, view definition, or user defined table function is
greater than 32766 or the definition contains a LOB and the sum of the
lengths specified on the ALLOCATE clause for varying-length fields and the
non-varying field lengths is greater than 32740. The maximum length is
reduced if any of the columns are varying-length or allow null values.

Is there any way to get around this? I am trying to create a .NET reporting
services report and have two very long comment fields that are needed in
view. Breaking it into two views isn't working for this report. Otherwise
is back to the drawing board.

Mike Wills

Check out my music show at
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by 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].