join tables sequencialy

Hi
I have 2 tables, with sea temp per date, how can i join 2 tables one with
data from 01/01/2008 until 30/03/2008 and another table with data from
01/03/2008 to 01/11/2008. i don't want to cut the tables and don't want to
use SQL, is it possible?

On Wed, 26 Nov 2008 05:26:08 -0800, Yossi evenzur wrote:

Hi
I have 2 tables, with sea temp per date, how can i join 2 tables one
with data from 01/01/2008 until 30/03/2008 and another table with data
from 01/03/2008 to 01/11/2008. i don't want to cut the tables and don't
want to use SQL, is it possible?

Get someone else to write the SQL for you? You need a Union query and
that requires writing a small amount of SQL.

SELECT * FROM TableA
UNION ALL SELECT * FROM TableB

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

so, no other option but SQL?

"Rick Brandt" wrote:

On Wed, 26 Nov 2008 05:26:08 -0800, Yossi evenzur wrote:

Hi
I have 2 tables, with sea temp per date, how can i join 2 tables one
with data from 01/01/2008 until 30/03/2008 and another table with data
from 01/03/2008 to 01/11/2008. i don't want to cut the tables and don't
want to use SQL, is it possible?

Get someone else to write the SQL for you? You need a Union query and
that requires writing a small amount of SQL.

SELECT * FROM TableA
UNION ALL SELECT * FROM TableB

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

On Wed, 26 Nov 2008 06:10:05 -0800, Yossi evenzur wrote:

so, no other option but SQL?

What is your objection to using SQL? I suppose you could insert both
tables into a third table with append queries and then display that.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

don't know SQL very well (hmmm, rimes), also tried your example and got an
error massage "Too many fields defined". both tables are identical, and i
want to have a single table without the overlapping entries, do i have to
union only the date field?

"Rick Brandt" wrote:

On Wed, 26 Nov 2008 06:10:05 -0800, Yossi evenzur wrote:

so, no other option but SQL?

What is your objection to using SQL? I suppose you could insert both
tables into a third table with append queries and then display that.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

On Wed, 26 Nov 2008 06:41:01 -0800, Yossi evenzur wrote:

don't know SQL very well (hmmm, rimes), also tried your example and got
an error massage "Too many fields defined". both tables are identical,
and i want to have a single table without the overlapping entries, do i
have to union only the date field?

Access will balk if the total of both tables exceeds 255 fields. If that
is what you have then your design is most likely messed up. If you
didn't want any duplicates in the output then you would use UNION instead
of UNION ALL, but you will have to resolve the (too many fields) problem
before it will work.


--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

Seems to me if you got "Too many fields defined", you would tell us how many
fields you have in your tables in the query. You should also provide the SQL
view of the query.

Is your date field unique/primary key in each of the tables? Do you really
want to exclude all records that are common to both tables or just display
one of the duplicate date records?
--
Duane Hookom
Microsoft Access MVP


"Yossi evenzur" wrote:

don't know SQL very well (hmmm, rimes), also tried your example and got an
error massage "Too many fields defined". both tables are identical, and i
want to have a single table without the overlapping entries, do i have to
union only the date field?

"Rick Brandt" wrote:

On Wed, 26 Nov 2008 06:10:05 -0800, Yossi evenzur wrote:

so, no other option but SQL?

What is your objection to using SQL? I suppose you could insert both
tables into a third table with append queries and then display that.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

the date field is not unique and i want to display one of the duplicate recodrs

"Duane Hookom" wrote:

Seems to me if you got "Too many fields defined", you would tell us how many
fields you have in your tables in the query. You should also provide the SQL
view of the query.

Is your date field unique/primary key in each of the tables? Do you really
want to exclude all records that are common to both tables or just display
one of the duplicate date records?
--
Duane Hookom
Microsoft Access MVP


"Yossi evenzur" wrote:

don't know SQL very well (hmmm, rimes), also tried your example and got an
error massage "Too many fields defined". both tables are identical, and i
want to have a single table without the overlapping entries, do i have to
union only the date field?

"Rick Brandt" wrote:

On Wed, 26 Nov 2008 06:10:05 -0800, Yossi evenzur wrote:

so, no other option but SQL?

What is your objection to using SQL? I suppose you could insert both
tables into a third table with append queries and then display that.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

hmmm, i couldn't understand from the help how union works, when i state
"union all" i'm forcing access to multiply the fields? if i have 5 fields in
both query, does union all creates a table with 10 fields?

"Rick Brandt" wrote:

On Wed, 26 Nov 2008 06:41:01 -0800, Yossi evenzur wrote:

don't know SQL very well (hmmm, rimes), also tried your example and got
an error massage "Too many fields defined". both tables are identical,
and i want to have a single table without the overlapping entries, do i
have to union only the date field?

Access will balk if the total of both tables exceeds 255 fields. If that
is what you have then your design is most likely messed up. If you
didn't want any duplicates in the output then you would use UNION instead
of UNION ALL, but you will have to resolve the (too many fields) problem
before it will work.


--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

On Wed, 26 Nov 2008 07:16:13 -0800, Yossi evenzur wrote:

hmmm, i couldn't understand from the help how union works, when i state
"union all" i'm forcing access to multiply the fields? if i have 5
fields in both query, does union all creates a table with 10 fields?

I believe in a UNION query the error is raised when there are too many
fields in the source tables. I don't think it matter how many fields are
in the output. Even though the output is combined vertically (by row
rather than column) the combined total of the fields in the input tables
cannot exceed 255.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com