Hello Helen,

HB> The way UNION is currently implemented, the structure of the output of the
HB> *first* SELECT statement sets up the structure for the all of the
HB> succeeding SELECTs. Your problem here is that the first SELECT produces an
HB> INTEREST_NAME column that is VARCHAR(6), while the succeeding one will
HB> output INTEREST_NAME values that will overflow a VARCHAR(6).

Let's suppose that INTEREST_NAME is defined as VARCHAR(30) in a DB.
Could you clarify please why filtering the field content should
"override"/substitute the field definition with VARCHAR(6) in the
output structure? Does the usage of 'SELECT *...' vs 'SELECT
INTEREST_NAME...' matter for the "overriding"?

Thanks.


--
Best regards,
Pavel Menshchikov
http://www.ls-software.com