(((Amoc_ExpandedFlight.UniqueID)=[Amoc_ExpandedFlight_1].[UniqueID]-1))
ORDER BY Amoc_ExpandedFlight.UniqueID;
'------------------------------------------------------------------------------
The executing code that effectively updates the average speed and climb/decent rate is also saved into an updating query:
'------------------------------------------------------------------------------
UPDATE Amoc_ExpandedFlight INNER JOIN AmocFlightUniqueIdPairs ON Amoc_ExpandedFlight.UniqueID = AmocFlightUniqueIdPairs.UID1 SET Amoc_ExpandedFlight.AvgSpeed = CalculateAvgSpeed([EventTime1],[EventTime2],[Lat1],[Lon1],[Lat2],[Lon2]), Amoc_ExpandedFlight.DeltaLevel = 6000*([Level1]-[Level2])/(DateDiff("s",Format([EventTime1],"yyyy-mm-dd hh:nn:ss"),Format([EventTime2],"yyyy-mm-dd hh:nn:ss")));
'------------------------------------------------------------------------------
3.2.3.1.16. Sub step 11.4 - Save the calculated fields in the flight table
To save the new calculated values in the flight table, a quick solution is used knowing that the flight table and the expanded flight table have the same structure and similar indexes. The flight table is deleted (object deletion, not just clearing table's contents) and then the expanded flight table is renamed as flight table. The used code is:
'------------------------------------------------------------------------------
DoCmd.DeleteObject acTable, "AmocFlight"
DoCmd.Rename "AmocFlight", acTable, "Amoc_ExpandedFlight"
'------------------------------------------------------------------------------
Doing so, the Amoc_ExpandedFlight table will not exist any more because it was renamed, so the next sub step will restore a new empty temporary expanded flight table, just for further use.
3.2.3.1.17. Sub step 11.5 - Empty (create) the temporary expanded flight table In this sub step a new empty temporary expanded flight table will be created, because in the previous sub step it was deleted (renamed). The code is:
'------------------------------------------------------------------------------
DoCmd.DeleteObject acTable, "Amoc_ExpandedFlight"
DoCmd.TransferDatabase acImport, "Microsoft Access", CurrentDb.Name, acTable, "Amoc_ExpandedFlight", "ModelFlight", True
'------------------------------------------------------------------------------
3.3. The Import AMOC tool interface
3.3.1. The Import AMOC tool menus
The Import AMOC tool menus are shown in Figure 52.
3.3.2. The Import AMOC tool interface
The Import AMOC files menu command will open the importing interface. This interface allows users to import AMOC generated text files automatically or manually. For each importing type there is an importing interface. Figure 53 and Figure 54 show these interfaces.
Figure 54: Manual import interface.
As it can be seen in these two figures, each step presented before is reflected in the interfaces. When the automatic importing is selected, all steps are executed one by one
without being possible to stop the process. If selecting the manual importing, it is possible to execute all the steps or just some of them. Of course some steps must be executed after other important steps were executed. For example if step 9 is executed before step 7 or 8, the calculated fluids might not be correct.
3.3.3. Import AMOC tool utilities
The tool provides also some utilities. These utilities can be accessed directly from the menu (Figure 52) or through another interface that is shown below in Figure 55. The utilities are shown in Figure 56, Figure 57, Figure 58, Figure 59, Figure 60, Figure 61, Figure 62 and Figure 63. 中国航空网 www.aero.cn 航空翻译 www.aviation.cn 本文链接地址：AERO2K Flight Movement Inventory Project Report(53)
