This paragraph describes the steps that must be followed in order to correctly import the ETMS provided text files.
3.3.1. Import ETMS tool task
Figure 64 illustrates the tool task.
Figure 64: Import ETMS tool task.

ETMS provided text files ImportETMS.mdb
Flight.txt
Flight_chord.txt

3.3.2. Importing steps
The steps to follow in order to import the ETMS text files are:

1.
Delete ETMS flight heads from the traffic table (empty the traffic table)

2.
Delete ETMS flight legs from the flight table (empty the flight table)

3.
Import ETMS traffic file (flight heads)

4.
Import ETMS flight file (flight legs)

5.
Link the two imported tables (link flight heads with their legs)

6.
Change airport codes to a preferred code (IATA)

7.
Consistency check (delete or correct inconsistent flight heads and legs)

8.
Change all Date/Time field values to GMT time

9.
Calculate the fluid (flight unique identifier)

10.
Split the flights that pass the midnight, inserting a new leg that has the EventTime hour 00:00:00

11.
Prepare data for merging

3.3.3. Describing the importing steps

In order to have a single day list of flights, the importing procedure must start with the deletion of all other flights that were imported previously. So in the first two steps the flight heads and legs will be deleted.
3.3.3.1. Step 1 - Delete ETMS flight heads from the traffic table
To delete the flight heads, three tables must be emptied. These tables are:
.
 ETMSTraffic.

.
 ETMS_ImportedTraffic.

.
 ETMS_InconsistentTraffic.

ETMSTraffic is the table that will store at the end of the importing procedure the flight
heads.
ETMS_ImportedTraffic is a temporary table that helps the process of importing the flight
heads.
ETMS_InconsistentTraffic is the table that will store at the end of the importing procedure
all inconsistent flight heads that must be deleted.

Each of the previous tables has a corresponding model table: ETMSTraffic – ModelTraffic  ETMS_ImportedTraffic – ModelETMS_ImportedTraffic  ETMS_InconsistentTraffic – ModelTraffic
These 2 tables are always empty, but they store the structure of the 3 tables described
before.
To empty the tables, the following code is used:

'--------------------------------------------------------------------------------
DoCmd.DeleteObject acTable, "ETMSTraffic"
DoCmd.TransferDatabase acImport, "Microsoft Access", CurrentDb.Name, acTable, "ETMSTraffic", "ModelTraffic", True
DoCmd.DeleteObject acTable, "ETMS_ImportedTraffic"
DoCmd.TransferDatabase acImport, "Microsoft Access", CurrentDb.Name, acTable, "ETMS_ImportedTraffic", "ModelETMS_ImportedTraffic ", True
DoCmd.DeleteObject acTable, "ETMS_InconsistentTraffic"
DoCmd.TransferDatabase acImport, "Microsoft Access", CurrentDb.Name, acTable, "ETMS_InconsistentTraffic", "ModelTraffic ", True
'--------------------------------------------------------------------------------

3.3.3.2. Step 2 - Delete ETMS flight legs from the flight table
To delete the flight legs, four tables must be emptied. These tables are:
.
 ETMSFlight.

.
 ETMS_InconsistentFlight.

.
 ETMS_ExpandedFlight.

ETMSFlight is the table that will store at the end of the importing procedure the flight legs.

ETMS_InconsistentFlight is the table that will store at the end of the importing procedure
all inconsistent flight legs that must be deleted.
　
中國航空網 www.k6050.com
航空翻譯 www.aviation.cn
本文鏈接地址：AERO2K Flight Movement Inventory Project Report(58)