query to import data from 2 tables into a third

[OTWarrior]

I have 3 tables, one for internal bookings, one for external bookings, and
one for the transport.

the transport is the focus here, and I need the other tables to export their
data into the transport table if the checkbox "boolNeedsTransport" is ticked
on the int' and ex booking tables. Once in the transport table, I can make
the transport bookings as normal, but the data in all 3 tables is very
different.

what is the best why of going about this? is it better to have the tables
separate and use another table in transport as a filter. Or to have a query
to pull the data when changed (this is a constantly moving database, and i
need it to update frequently).

any help would be greatly appreciated.

 

[Amy Blankenship]

I have 3 tables, one for internal bookings, one for external bookings, and
one for the transport.

the transport is the focus here, and I need the other tables to export
their
data into the transport table if the checkbox "boolNeedsTransport" is
ticked
on the int' and ex booking tables. Once in the transport table, I can make
the transport bookings as normal, but the data in all 3 tables is very
different.

what is the best why of going about this? is it better to have the tables
separate and use another table in transport as a filter. Or to have a
query
to pull the data when changed (this is a constantly moving database, and i
need it to update frequently).

The best thing to do is to have the data combined into one table and then
set a flag as to what "state" it is in.

HTH;

Amy

 

[gumby]

I have 3 tables, one for internal bookings, one for external bookings, and
one for the transport.

the transport is the focus here, and I need the other tables to export their
data into the transport table if the checkbox "boolNeedsTransport" is ticked
on the int' and ex booking tables. Once in the transport table, I can make
the transport bookings as normal, but the data in all 3 tables is very
different.

what is the best why of going about this? is it better to have the tables
separate and use another table in transport as a filter. Or to have a query
to pull the data when changed (this is a constantly moving database, and i
need it to update frequently).

any help would be greatly appreciated.

You may want to start over and only have one table. Regardless of
wether it is a internal and external, you could query the
booNeedsTransport and report it sperately. This would keep your table
constantly updated.

David

 

[John W. Vinson]

I have 3 tables, one for internal bookings, one for external bookings, and
one for the transport.

the transport is the focus here, and I need the other tables to export their
data into the transport table if the checkbox "boolNeedsTransport" is ticked
on the int' and ex booking tables. Once in the transport table, I can make
the transport bookings as normal, but the data in all 3 tables is very
different.

what is the best why of going about this? is it better to have the tables
separate and use another table in transport as a filter. Or to have a query
to pull the data when changed (this is a constantly moving database, and i
need it to update frequently).

any help would be greatly appreciated.

I agree with Amy and Gumby that you really should not have two tables for
bookings, unless they have altogether different structures. In addition,
though, it sounds like you're copying data from the booking tables into the
transport table. If so, you're not making proper use of the relational
capabilities of Access! You should have the data in each table stored only in
that table; a Booking is a Booking, and the Booking table should contain all
the booking data; Transport is a different type of entity (*not* a booking!)
and should probably contain only a foreign key linking it to the booking for
which transport is needed.

You would then use Queries to link the data together. It is neither necessary
nor appropriate to export data from one table into another table!

John W. Vinson [MVP]