Inconsistent Behaviour of Union Select Query

  • Thread starter Thread starter Doug Robbins
  • Start date Start date
D

Doug Robbins

Using Access 2003, I have a Union Select query to combine information from
two separate tables. In one of the tables there are two records that in one
field have the same value that happens to be the number 10,000. The Union
Select query ignores one of these records. However, if I change the value
of the entry in that field for the record that is ignored to 10,000.01, the
record is then included in the result of the Union Select Query.

Can anyone explain why the record would be ignored when it contains the
value of 10,000?
 
Hi Doug. Good to hear from you in this neck of the woods. :-)

By default, a UNION query will de-duplicate.
To get all records, use UNION ALL, e.g.

SELECT * FROM Table1
UNION ALL
SELECT * FROM Table2;
 
Doug said:
Using Access 2003, I have a Union Select query to combine information from
two separate tables. In one of the tables there are two records that in one
field have the same value that happens to be the number 10,000. The Union
Select query ignores one of these records. However, if I change the value
of the entry in that field for the record that is ignored to 10,000.01, the
record is then included in the result of the Union Select Query.

Can anyone explain why the record would be ignored when it contains the
value of 10,000?
Click to expand...
UNION is distinct, use UNION ALL

Olli
 
Thanks, Allen.

Live and Learn.

--
Hope this helps.

Please reply to the newsgroup unless you wish to avail yourself of my
services on a paid consulting basis.

Doug Robbins - Word MVP
Allen Browne said:
Hi Doug. Good to hear from you in this neck of the woods. :-)

By default, a UNION query will de-duplicate.
To get all records, use UNION ALL, e.g.

SELECT * FROM Table1
UNION ALL
SELECT * FROM Table2;
Click to expand...
 
Back
Top