Operating with Multiple Callsigns or from Multiple Locations
QSOs and their information items are stored in a log file. DXKeeper assumes that all QSOs in a log file are valid for the same ARRL DXCC, Islands On the Air (IOTA), CQ DX Marathon, CQ Worked All Zones (WAZ), and CQ Worked All Prefixes (WPX) awards. If you've operated from multiple locations, DXKeeper provides a mechanism that enables you to specify which of those locations are valid for ARRL VHF/UHF Century Club (VUCC) and ARRL Worked All States (WAS) awards.
When you run DXKeeper for the first time after installing it, you will be prompted to specify your current callsign. DXKeeper uses this callsign to create a log file in your DXKeeper folder's Databases sub-folder, and automatically opens that log. If you installed DXKeeper in the folder c:\DXLab\DXKeeper and your callsign is VE3KI, for example, DXKeeper will create and open the file c:\DXLab\DXKeeper\VE3KI.mdb. This log file may be all you ever need, as QSOs made with other callsigns you hold or have held can be recorded in this log file if they were made from the same DXCC entity (and thus count towards the same awards). Use the Station Callsign box on the Configuration window's Defaults tab to specify the callsign you are currently using when making QSOs. When importing QSOs from an ADIF file, use the the Replacement options panel's Station Callsign box to specify the callsign you used when making the QSOs to be imported.
If you have operated from multiple DXCC entities, however, you should use a separate log file for the QSOs made from each entity. You should also maintain a separate log to record QSOs made from your current DXCC entity that don't count towards the awards you're pursuing; examples include QSOs made at a club station or by a station for whom you serve as QSL Manager. Controls in the Configuration window's Log File panel support this mode of operation by enabling you to
- create an empty new log and then open it
- select an existing log by navigating with a Windows file selector or by typing its pathname, and then open it
If you're managing QSOs for a club station or serving as a QSL manager, you can maintain separate settings for each role and switch among them.
If you start DXKeeper with a command line argument that specifies a valid pathname, DXKeeper will attempt to open the designated file as a log. You can use this to setup desktop icons that when double-clicked cause DXKeeper to start with the appropriate log file already opened.
If you operate or have operated from multiple QTHs and wish to automatically generate QSL cards or labels that correctly reflect the QTH from which you were operating , DXKeeper enables you to specify the details of each QTH (e.g. city, country, state, grid) and assign each QTH a unique identifier that can be logged with a QSO. This same mechanism can also distinguish QTHs that are valid for VUCC and WAS awards from QTHs that aren't valid for these awards.
Here's an example of how multiple callsigns and multiple QTHs can be handled:
Valid for VUCC
Valid for WAS
Los Altos CA, USA
novice license callsign, previous QTH
Los Altos CA, USA
general license callsign, previous QTH
Los Altos CA, USA
present license callsign, previous QTH
Wayland, MA, USA
present license callsign, present QTH
holiday callsign, holiday QTH
eQSL.cc requires you to setup separate accounts for each location from which you've operated, assign each account a unique Nickname, and specify the appropriate Nickname when submitting QSOs made from a particular location. Procedures for accomplishing this are provided here.
LoTW requires you to obtain a Callsign Certificate for each callsign you've used over the air, and a Station Location for each QTH from which you've operated, and select the correct Callsign Certificate and Station Location when submitting QSOs or synchronizing status. Procedures for accomplishing this are provided here.