Thank you for the tip on the normalization.
I have a few questions concerning the tables and the normalization.
-When a field can be a combination of numbers and lettre (example : latitude in decimal). What's the best field type? short text or number?
-I've attached the database for you to have a look. Because I'm not entirely sure of what I'm doing.
In my project :
I've created a table (tbl_Airport_info) where each airport is identified by a unique ICAO (4-lettre code), so I've set ICAO to be a primary key so that all the field of that table depend on a unique ICAO.
In a second table (tbl_Runway), an airport can have multiple runways (each runway has a unique number), so I set the runwayname as a primary key and called another field ICAO. Therefore, the runwayname is unique and depend on the ICAO. And the field ICAO in this tables makes it possible to have a relation between the airport and the runway tables. I am correct?
Following this logic, I've created a tables (tbl_Obstacles), where a runway can have multiple obstacles. In this table, I've set the ObstacleID (autonumber) has a primary key, and added a field runwayname. This allows a relation between the tbl_Obstacles and runwayname (because a unique runway can have multiple obstacles). I am correct?
Also, I've created a table (tbl_Procedure) where a unique runway can have multiple procedure. Therefore, I created a ProcedureID (autonumber) has a primary key, and added a field runwayname. This allows a relation between the table tbl_Runway and the table tbl_Procedure. I am correct?
This one, is not clear in my head. Each airport can have multiple aircraft (planes) assigned to it. Should I create a new table (tbl_Aircraft) where I set a AircraftID (autonumber) has a primary key and add two field ICAO and Actype (name I chosen for the aircraft type). Isn't there a better way? Because for example, 5 airport have 5 aircraft. That means I'll have 25 lignes to do. In the final database, we'll have hundreds of airport, so that could mean thousands of lignes.
I am understanding the method correctly?
Please excuse me for the jargon. I hope I was clear enough. Please let me know if you have any questions and feel free to make a comment on the database.
I have a few questions concerning the tables and the normalization.
-When a field can be a combination of numbers and lettre (example : latitude in decimal). What's the best field type? short text or number?
-I've attached the database for you to have a look. Because I'm not entirely sure of what I'm doing.
In my project :
I've created a table (tbl_Airport_info) where each airport is identified by a unique ICAO (4-lettre code), so I've set ICAO to be a primary key so that all the field of that table depend on a unique ICAO.
In a second table (tbl_Runway), an airport can have multiple runways (each runway has a unique number), so I set the runwayname as a primary key and called another field ICAO. Therefore, the runwayname is unique and depend on the ICAO. And the field ICAO in this tables makes it possible to have a relation between the airport and the runway tables. I am correct?
Following this logic, I've created a tables (tbl_Obstacles), where a runway can have multiple obstacles. In this table, I've set the ObstacleID (autonumber) has a primary key, and added a field runwayname. This allows a relation between the tbl_Obstacles and runwayname (because a unique runway can have multiple obstacles). I am correct?
Also, I've created a table (tbl_Procedure) where a unique runway can have multiple procedure. Therefore, I created a ProcedureID (autonumber) has a primary key, and added a field runwayname. This allows a relation between the table tbl_Runway and the table tbl_Procedure. I am correct?
This one, is not clear in my head. Each airport can have multiple aircraft (planes) assigned to it. Should I create a new table (tbl_Aircraft) where I set a AircraftID (autonumber) has a primary key and add two field ICAO and Actype (name I chosen for the aircraft type). Isn't there a better way? Because for example, 5 airport have 5 aircraft. That means I'll have 25 lignes to do. In the final database, we'll have hundreds of airport, so that could mean thousands of lignes.
I am understanding the method correctly?
Please excuse me for the jargon. I hope I was clear enough. Please let me know if you have any questions and feel free to make a comment on the database.