Differences between revisions 14 and 15
⇤ ← Revision 14 as of 2022-11-25 19:29:08 →
Size: 3220
Editor: AA6YQ
Comment:
← Revision 15 as of 2022-11-25 19:29:29 → ⇥
Size: 3221
Editor: AA6YQ
Comment:
Deletions are marked like this. Additions are marked like this.
Line 22: Line 22:
    a. use the '''Substitution Options''' and '''Replacement Options''' panels on the '''Import QSOs''' tab of DXKeeper's Main window to provide information to recorded by FLE     a. use the '''Substitution Options''' and '''Replacement Options''' panels on the '''Import QSOs''' tab of DXKeeper's Main window to provide information not recorded by FLE

Logging Completed QSOs

There are three effective ways to log already-completed QSOs from a paper logbook or from notes made during an operating session:

  1. use the Main window of DXKeeper's Log QSOs tab with the Optimize for realtime QSO entry option disabled (Configuration window, General tab, Main "Log QSOs" options panel)

    1. entry errors (e.g. invalid frequencies or modes) are flagged immediately
    2. information obtained from previous QSOs, database lookups, and callbook queries (if enabled) is immediately visible

    3. see Logging and Managing QSOs and Logging Completed QSOs for detailed information and capabilities

    4. the use of Keyboard Shortcuts will dramatically speed QSO entry; give yourself time to become familiar with these shortcuts

  2. use DF3DB's excellent Fast Log Entry (FLE) application to generate an ADIF file, and then direct DXKeeper to import the generated ADIF file

    1. entry errors (e.g. invalid frequencies or modes) are flagged when the ADIF file is imported
    2. information obtained from database lookups and callbook queries (if enabled) is only visible after the ADIF file is imported

    3. use the Substitution Options and Replacement Options panels on the Import QSOs tab of DXKeeper's Main window to provide information not recorded by FLE

    4. when using FLE for the first time, record the first 10 QSOs, direct FLE to generate an ADIF file, and then direct DXKeeper to import that file to confirm that all is working as expected

  3. use a spreadsheet application to generate a tab-delimited file in the correct format, and then direct DXKeeper to import the generated tab-delimited file

    1. to generate a prototype tab-delimited file in the correct format, log a test QSO and direct DXKeeper to export that QSO to a tab-delimited file

    2. entry errors (e.g. invalid frequencies or modes) are flagged when the tab-delimited file is imported
    3. information obtained from database lookups and callbook queries (if enabled) is only visible after the tab-delimited file is imported

The user with many QSOs to enter but no strong preference should try all three options and pick the one that works best.

Recording Information Required by Awards

Post a question or suggestion on the DXLab Discussion Group

Displaying QSOs

Logging

Getting Started with DXLab

LogCompletedQSOs (last edited 2022-11-25 19:29:29 by AA6YQ)