If you have decided to make FRLogger your logging home then most of you will want to import prior logs into FRLogger. FRLogger provides support for ADIF import and export via the Database Administrator Menu. Click on the top menu bar where your database is shown and select Database Administrator.
There are two ways to import ADIF data into FRLogger:
- Interactive (left side) - Allows you to review and manually commit the import.
- Large Import (right side) - Allows import of very large files.
The interactive import is a three step process.
- Select an ADIF file to import
- Read the imported file into memory
- Review, correct and commit the import
This interactive import process will read your ADIF import file into memory. It will then show you a list of the QSOs that will be imported. You can delete or correct individual items. And finally, you can commit them to your database.
Because of the need to read this data into memory it will not work with a large number of ADIF records to import. Knowing whether to try the interactive or go straight for the large import depends upon the following factors:
- RAM - IF your computer does not have much RAM, choose the large import
- If you don't care to review or edit the imports, choose the large import
- If you have perhaps more than 10,000 log entries, choose the large import
- If you try the interactive import and it freezes or crashes, try the large import
If you decide to use the interactive import after you have done steps 1 and 2, keep in mind that your data is not in your database yet! You must review the list, fix any errors if desired, then commit using the "Commit QSOS to database" button.
At times people want to export their QSO data. The export tab provides this functionality and exporting your database to ADIF is a good way to back it up. You can also choose to post your QSOs to online services you have enabled on the export tab.
You can choose to export all records or records that match a date range. You can also choose to export all fields or just the minimal set needed for services like LOTW.
For both import and export there are script processing options. To use these requires a detailed an in depth knowledge of the scripting language and the process needed to handle import and export. These script options will be covered in a later scripting guide.
Many of us post our contacts to online logs like ClubLog or HRDLog. At times, perhaps due to no network being available or the service being down, our contacts did not get posted to the service. The post feature allows you to select contacts in a small date range and send them off to your online logbook.
I do not recommend you do this for large date ranges as it will generate a very large number of post requests to the service. Please be kind to your online services and work in small, perhaps 1 day, date ranges.
The maintenance tab on the database administor dialog allows you to scan for and make minor fixes to your log. There are a number of options for scanning your log:
- Scan QSOs for possible issues - This tries to detect QSOs that have missing grids, dates, times, bands, frequencies or modes
- Process QSOs through script - This will be covered in the scripting guide at a later time
- Scan QSOs for possible duplicates - This looks at call, date, time, frequency, mode and tries to see if there could be duplicates
- Clear all QSO issue flags - If you don't care and you just want to clear the issues, you can use this option
Please be aware that each of these options can take significant time to run if your database is large. If your database is very large some of them may fail to work entirely because of memory issues.
Scan QSOs for possible issues
This will scan your log and display for you any QSO that is missing some data. After the scan is complete you should receive a list that looks like the following:
As you can see, in my log, I have some entries that are missing band, mode, gridsquare etc. On each line there are buttons that allow me to edit, delete, clear duplicate and clear errors. These buttons will affect the specific QSO in that you pressed the button on.
The edit button allows you to actually edit your QSO and make manual fixes. Most of the other buttons are pretty obvious how they work.
For the lazy people amoung us there is a "Clear all QSO issue flags" button that will just say, I don't care, just fix them all.
Scan QSOs for possible duplicates
This process will take the longest. On my somewhat small 1100 QSO database it took close to 2 minutes to run! For each QSO in your database it will attempt to compare it against ALL other QSOs to determine if there is a duplicate.
Generally with duplicate QSOs you want to look at each and decide which one is more accurate and delete the other QSO. This is pretty much a slow manual process if you have a lot of duplicates.
Other tabs on the database administrator
You will see that there are other tabs on the database administrator dialog. Some of these are works in progress or have nothing on them. One tab that does have content is "Misc".
The Misc tab allows you to update lists from sources on the web. FRLogger uses these lists when displaying data to you. If you use any of these clubs or services you should reload their lists periodically.