OK, not much of an access person so this could be really easy.
Table a is a list of airports, table b is a list of flights.
A flight has a departure airport, and an arrival airport.
table: airports
(primary key): apt_id
table: flights
(primary key): flt_id
attribute: dep_apt
attribute: arr_apt
I've already set it such that when you enter the arrival/departure airport it's a lookup from the airports table - but what I am trying to do is establish referential integrity on both relationships.
If I create the first, and establish referential integrity it works just fine, but when I create the second - access creates a second table (airports_1) for the new link(but it does establish referential integrity).
If I add them to the same link I am unable to enforce referential integrity receiving the standard check that your key is unique error.
I can create a link from airports.apt_id to flights.dep_apt and establish ref. integrity just fine.
I can create a link from airports.apt_id to flights.arr_apt and extablish ref. integrity just fine.
It's only mad when I want both at the same time, where does this leave me?
Start Free Trial
