Steve: Thank you.

In my posting of the helpFiles' UNION syntax, I formatted RBTI's "collist" by my coding concatenation rule:

(Courier New font )

collist = col[umn]list = [ col + list ] = colList

Choice of font makes the difference.

I'll give it a shot without the USING clause and let you know.

Happy New Year!, Bruce

Bruce A. Chitiea
Treasurer, fy2023/25
------------------------
Rotary Club of Walnut Valley
Walnut  Valley Rotary Foundation
----------------------------------------
PO Box 5453 | Diamond Bar CA 91765-7453
[email protected]  |  (909) 238-9012 m

------ Original Message ------
From [email protected]
To [email protected]
Date 1/7/2025 7:45:59 PM
Subject RE: [RBASE-L] - Digest for [email protected] - 3 updates in 1 topic

Bruce,



Two thoughts.



Is COLLIST (colList ) spelled correctly? Looks like there is an upper case i in your statement.



Try it without the USING clause and see what happens. The result should be both tables with all columns in the third table.



sjohnson







From: [email protected] <[email protected]>
Sent: Tuesday, December 17, 2024 7:18 AM
To: Digest recipients <[email protected]>
Subject: [RBASE-L] - Digest for [email protected] - 3 updates in 1 topic



[email protected] <https://groups.google.com/forum/?utm_source=digest&utm_medium=email#!forum/rbase-l/topics>

Google Groups <https://groups.google.com/forum/?utm_source=digest&utm_medium=email/#!overview>

Google Groups Logo
<https://groups.google.com/forum/?utm_source=digest&utm_medium=email/#!overview>

Topic digest
View all topics <https://groups.google.com/forum/?utm_source=digest&utm_medium=email#!forum/rbase-l/topics>

ยท        UNION Fail <#group_thread_0> - 3 Updates

UNION Fail <http://groups.google.com/group/rbase-l/t/861a8a6a7652ab87?utm_source=digest&utm_medium=email>

Bruce Chitiea <[email protected]>: Dec 16 07:45PM

All: RGB11

Can't say I've ever seen this. This UNION structure outputs a table
containing only the contents of tableName1_tt (production table names
changed for this discussion):

UNION tableName1_tt +
WITH tableName2_tt +
FORMING TEMP tableName3_tt +
USING +
line0_entityID, +
line1_addressee, +
line2_streetAddress, +
line3_cityStateZip

Of note:
- no error message is thrown
- all three tables are temp tables
- all production table names are legally formed
- tableName1_tt and tableName2_tt have the same number of columns
- column names are the same, arranged in the same order, in both tables
- each set of named columns has the same datatype
- both input tables are generated without error
- tableName3_tt contains only the rows from tableName1_tt

Syntax:
UNION tableName1 WITH tableName2 FORMING TEMP tableName3 USING colList

Huh. Should be childs-play. Any thoughts? And thanks.

Bruce A. Chitiea
SafeSectors, Inc.
1142 S Diamond Bar Blvd # 442
Diamond Bar CA 91765-2203

[email protected]
(909) 238-9012 m

Daniel Goldberg <[email protected]>: Dec 16 09:27PM

Is one of the using columns in both tables?

USING collist
Specifies the columns and order of columns that you want to include in the new table. At least one column in the USING clause must exist in both tables. If you do not include the clause, R:BASE makes a new table that includes all columns from both tables.



Dan Goldberg



From: [email protected] <[email protected]> On Behalf Of Bruce Chitiea
Sent: Monday, December 16, 2024 11:45 AM
To: [email protected]
Subject: [EXTERNAL] [RBASE-L] - UNION Fail

All: RGB11

Can't say I've ever seen this. This UNION structure outputs a table containing only the contents of tableName1_tt (production table names changed for this discussion):

UNION tableName1_tt +
WITH tableName2_tt +
FORMING TEMP tableName3_tt +
USING +
line0_entityID, +
line1_addressee, +
line2_streetAddress, +
line3_cityStateZip

Of note:
- no error message is thrown
- all three tables are temp tables
- all production table names are legally formed
- tableName1_tt and tableName2_tt have the same number of columns
- column names are the same, arranged in the same order, in both tables
- each set of named columns has the same datatype
- both input tables are generated without error
- tableName3_tt contains only the rows from tableName1_tt

Syntax:
UNION tableName1 WITH tableName2 FORMING TEMP tableName3 USING colList

Huh. Should be childs-play. Any thoughts? And thanks.

Bruce A. Chitiea
SafeSectors, Inc.
1142 S Diamond Bar Blvd # 442
Diamond Bar CA 91765-2203

[email protected]<mailto:[email protected]>
(909) 238-9012 m

--
For group guidelines, visit http://www.rbase.com/support/usersgroup_guidelines.php
---
You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:rbase-l+unsubscribe <mailto:rbase-l%2Bunsubscribe>@googlegroups.com>. To view this discussion visit https://groups.google.com/d/msgid/rbase-l/em77665026-a5d8-450b-a3b0-3dfaee82dbfe%40a413b759.com<https://groups.google.com/d/msgid/rbase-l/em77665026-a5d8-450b-a3b0-3dfaee82dbfe%40a413b759.com?utm_medium=email&utm_source=footer>.

Bruce Chitiea <[email protected]>: Dec 16 09:34PM

Thank you, Dan. All columns exist in both tables.

Bruce


------ Original Message ------
From "'Daniel Goldberg' via RBASE-L" <[email protected]>
To "[email protected]" <[email protected]>
Date 12/16/2024 1:27:12 PM
Subject RE: [EXTERNAL] [RBASE-L] - UNION Fail

>To view this discussion visit
>https://groups.google.com/d/msgid/rbase-l/em77665026-a5d8-450b-a3b0-3dfaee82dbfe%40a413b759.com
><https://groups.google.com/d/msgid/rbase-l/em77665026-a5d8-450b-a3b0-3dfaee82dbfe%40a413b759.com?utm_medium=email&utm_source=footer>.

--
For group guidelines, visit
http://www.rbase.com/support/usersgroup_guidelines.php
---
You received this message because you are subscribed to the Google
Groups "RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/rbase-l/BY3PR19MB5027507509D2B35245052B32D43B2%40BY3PR19MB5027.namprd19.prod.outlook.com
<https://groups.google.com/d/msgid/rbase-l/BY3PR19MB5027507509D2B35245052B32D43B2%40BY3PR19MB5027.namprd19.prod.outlook.com?utm_medium=email&utm_source=footer>.

Back to top

You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page <https://groups.google.com/forum/?utm_source=digest&utm_medium=email#!forum/rbase-l/join>. To unsubscribe from this group and stop receiving emails from it send an email to [email protected].




--
For group guidelines, visit http://www.rbase.com/support/usersgroup_guidelines.php
---
You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/rbase-l/015901db617f%24d4ea7e40%247ebf7ac0%24%40sprintmail.com <https://groups.google.com/d/msgid/rbase-l/015901db617f%24d4ea7e40%247ebf7ac0%24%40sprintmail.com?utm_medium=email&utm_source=footer>.

--
For group guidelines, visit 
http://www.rbase.com/support/usersgroup_guidelines.php
--- You received this message because you are subscribed to the Google Groups "RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/rbase-l/emaeac1446-7d5d-46d3-8448-5bf22583167a%40cfbc7a66.com.

Reply via email to