data from 2 tables into another, and manipulating

[OTWarrior]

I have 2 tables which have their own field names, but are similar to each
other, and I need these 2 to be exported/linked to a third table. This third
table wil be used to do a booking (the other tables are used for additional
different kinds of booking also), and I will need to be able to set the
"booking" from the original table in the new table to be completed.

Is there an easy way of bringing data from one table to another, when the
destination table has more fields (and in some cases different field names),
(ie: a query of sorts)

 

[Amy Blankenship]

I have 2 tables which have their own field names, but are similar to each
other, and I need these 2 to be exported/linked to a third table. This
third
table wil be used to do a booking (the other tables are used for
additional
different kinds of booking also), and I will need to be able to set the
"booking" from the original table in the new table to be completed.

Is there an easy way of bringing data from one table to another, when the
destination table has more fields (and in some cases different field
names),
(ie: a query of sorts)

If you instead tell us what the business requirement is, we can probably
give you a better table design than what you have. In a properly normalized
table structure, there is no need to copy stuff from table to table.

HTH;

Amy

 

[John W. Vinson]

I have 2 tables which have their own field names, but are similar to each
other, and I need these 2 to be exported/linked to a third table. This third
table wil be used to do a booking (the other tables are used for additional
different kinds of booking also), and I will need to be able to set the
"booking" from the original table in the new table to be completed.

Is there an easy way of bringing data from one table to another, when the
destination table has more fields (and in some cases different field names),
(ie: a query of sorts)

An Append query, to be precise.

But I fully agree with Amy that the question suggests a flawed design! Please
answer her question - this operation should almost surely *not* be necessary.

John W. Vinson [MVP]

 

[OTWarrior via AccessMonster.com]

unfortunately, there are 4 different divisions to the team, and 4 sections of
the database, and I have to bring the information from 2 of them into the
third. All I need to bring is the autonumber (to link the third autonumber
and the other bookings together) and the dates across to help make it easier

I have 2 tables which have their own field names, but are similar to each
other, and I need these 2 to be exported/linked to a third table. This third

[quoted text clipped - 5 lines]

destination table has more fields (and in some cases different field names),
(ie: a query of sorts)

An Append query, to be precise.

But I fully agree with Amy that the question suggests a flawed design! Please
answer her question - this operation should almost surely *not* be necessary.

John W. Vinson [MVP]

 

[John W. Vinson]

unfortunately, there are 4 different divisions to the team, and 4 sections of
the database, and I have to bring the information from 2 of them into the
third. All I need to bring is the autonumber (to link the third autonumber
and the other bookings together) and the dates across to help make it easier
on the user.

You have four logical divisions to the data.

The properly normalized way to handle this is not to have four tables, with
four competing autonumber values, but to have the data stored in ONE table,
with a field indicating the division. You can then use a Query selecting one
of the divisions for all queries having to do with that division.

Having your tables properly normalized is more of a chore for the developer
but makes it easier for the user in the end.


John W. Vinson [MVP]

 

[Amy Blankenship]

You have four logical divisions to the data.

The properly normalized way to handle this is not to have four tables,
with
four competing autonumber values, but to have the data stored in ONE
table,
with a field indicating the division. You can then use a Query selecting
one
of the divisions for all queries having to do with that division.

Having your tables properly normalized is more of a chore for the
developer
but makes it easier for the user in the end.

I think he means it is a political problem, and that there are four
different groups working on the database. Too many cooks...