| A | Note: The import field mapping suggestions given below are from a test import from Logbook Pro version 1.9.3. Certain field mappings may not apply to earlier or later versions of Logbook Pro. Logbook Pro™ uses a Microsoft Access™ database format to store pilot records. Therefore, data can be imported into AeroLog Pro via the ODBC Import feature. The following procedures will guide you through creating an ODBC Data Source for the import, and mapping the Logbook Pro fields into AeroLog Pro. Creating a Data Source - Start AeroLog Pro, open the Pilot Logbook window, and select the Import tab.
- Click ODBC Import.
- Click Add button to create new data source.
- Select "Microsoft Access Driver (*.mdb) from the ODBD Drivers dialog, then click OK. The ODBC Microsoft Access Setup dialog will appear.
- Enter a Data Source Name (e.g. "Logbook Pro").
- Click the Select button to open the Select Database dialog.
- Change the List Files of Type field at the bottom to "All Files".
- Locate the Logbook Pro folder in the folder list on the right, and select it. (The default folder is C:Program FilesLogbook Pro.)
- Locate your logbook database (file extension is "LBK") in the list on the left, and double-click on it.
- Click the OK button to close the ODBC Microsoft Access Setup dialog.
Opening the Data Source - Locate the new "Logbook Pro" data source in the list at the top of the ODBC Import window, and click on the "+" to the left.
- Click the "+" to the left of "Tables".
- Locate "tblLog" and click on it to select it. The data records will be displayed at the bottom.
- Review the displayed data, and make notes of any custom fields you want to map into AeroLog Pro.
- Click Next at the bottom to go to page 2 of the ODBC Import wizard.
Mapping the Fields Note: The following field map includes the "standard" logbook fields. You will most likely need to make changes or additions to this list in order to accommodate your specific logbook layout. Drag and drop the Data Source Field (Logbook Pro) to the AeroLog Pro fields as follows: | AeroLog Pro Field | Logbook Pro Field | | Date | LogDate | | Aircraft ID | AircraftIdent | | Make/Model | Aircraft | | Route | RouteFrom {see note below} | | Duration | Duraiton | | Day T/O | LandDay | | Day Ldg | LandDay | | Nit T/O | LandNight | | Nit Ldg | LandNight | | Dep. Time | TimeOUT |
Arr.Time | TimeIn | | Apch -ILS-Unknown | ILS | | Apch-VOR-Unknown | VOR | | Apch - GPS -Unknown | GPS | | Apch - NDB -Unknown | NDB | | Apch - LOC -Unknown | LOC | | Apch- LOCBC -Unknown | BC | | Apch-ASR-UnknownASR | | Remarks | Remarks | | Holds | holding | | Night | CondNight | | Actual | CondInstrument | | Hood | CondSimInstrument | | X-Cntry | CrossCountry | | Primary Solo | Solo | | PIC | PIC | | SIC | SIC | | th="50%">Primary Dual | Dual |
Note --Logbook Pro appears to store the entire "route" (list of airport identifiers) in the RouteFrom field. Mapping this to the Route field in AeroLog Pro will cause the From, To and Via fields to be properly set. Completing the Import - Map any additional fields to AeroLog Pro custom fields as necessary.
- Click Next
- Select the desired default values as appropriate to your flying.
- Click Next
- Click the Start Import button.
', 'Logbook Pro,Import,ODBC', 'admin', '2003-03-14');
INSERT INTO faq VALUES (10, '2', 'How do I make a "lump sum" entry of my previous flight time?', 'To enter previous flight information without entering each flight, you need to group fights according to aircraft classification then total each group and enter it as one "long" flight. The more detailed your grouping is, the more detail you will retain in your Tally Sheet totals (and the more work you have to do). Let''s take a simple example. Say the last page of your first logbook shows the following totals. Landings: 594
Day: 235.4
Dual: 81.5
Inst App: 66
Night: 22.7
PIC: 78.0
AIR-SEL: 255.7
Hood: 43.3
X-Country: 136.2
Actual: 3.7
Total Time: 255.7 Looking at the totals, you can tell right off that all time was spent in Airplane-SEL aircraft since this total is the same as the flight time total. This means you can be really lazy and get away with one multiple-flight record for a single engine land airplane (Category=AIR and Class=SEL). Even with one record, you still have to flip through the book to get information on how to divide the totals in the breakdown table (e.g., how many landings are at night, etc.). This grouping gives more detail than the original logbook, but far from the detail possible with AeroLog. There is no breakdown by make/model (type) since all flights in the various types of aircraft are lumped together. To include this level of detail, you would have to scan through your logbook and calculate a separate set of totals for each type of aircraft you have flown. The number of different types would determine how many multiple-flight records you would need to create. The finer you make your groupings, the more work is
involved. Essentially you are doing by hand, what AeroLog does for you automatically when you enter each flight. At some point it becomes so involved that it will take less time to enter all the flights from the beginning. The bottom line is detail. The more you want, the more time and effort you have to put into the process. If you are short on time (and who isn''t these days) you can establish a baseline using a few multiple-flight records to start. As time becomes available, you can gradually replace each multi-flight record with the individual flight records it represents. |
