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 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 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 thetab-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.


Post a question or suggestion on the DXLab Discussion Group

Displaying QSOs

Logging

Getting Started with DXLab

LogCompletedQSOs (last edited 2018-07-05 20:23:22 by AA6YQ)