if you don't need relationships then its doubtful you need to use a relational db in the first place
relational integrity is more about enforcing rules on data to make certain its more coherent, more accurate, more reliable. a relationship enforced in a db doesn't by it self do anything magical (you could enforce the same rules in software), you have to have more trust in your users, you have moire code to testr and verify).
if you haven't alrady enforced relationships then now is a pretty good timne to do so, but you may well get data aerrors stopping you imposing relationships.
you can define what effectively is a temporary relatiosnhip in the query designer (it will work only when ever that query is executed) by clicking and dragging accross columns/tables to define such a relationship. but such relationships are not as powerfull or flexible as a true table level relationship definition. they wont do anythign to stop you stuffing in bad data
effectively what you want is a join
select my, column, list from TakeOffStuff as TO
join LandingStuff as LS on LS.FlightID = TO.FlightID
join InflightStuff as IS on IS.FlightID = TO.FlightID
access join syntax is a little different to standard SQL so youmay well need to teweak the above. if you can create your links int he query dewsigner do so, it will make your life easier
in true relational terms you probably ought to have another table Flights, whcih stores everything that is pertinent to the flight including the flight number, which should be the primary key. from that you have your 3 current tables all using the flight number as a foreign key to flights
I'd rather be riding on the Tiger 800 or the Norton