DOS Country/Prefix Updates - (06/19/99)
 

   This zip file includes (3) .db files.  The (3) .db files included are:  callmap.db, mappfx.db and pripfx.db.  Updating these (3) .db files, however, is actually the last of (3) suggested steps.

    First, and most importantly, it is recommended that you back-up all of your dxbase .db files before doing anything else.  Dxbase for DOS has a handy built-in method for doing so via the Archive Program (see pg. 29 of the manual).

    Second, it is recommended that you prepare several reports utilizing the Standard Reports/QSO's in a Country function.  In particular, it is suggested that you prepare reports of at least your QSO's with FO, VR6, and VS.  There may be others for which you may wish to similarly prepare reports.  (NOTE:  remember to rename each report after it is prepared or otherwise it will be written over each time.)  These reports will be handy when it comes time, after you have updated the (3) .db files, to go back and change the PFX for each affected QSO.  In conformity with the .db prefix used for Clipperton, I utilized FO/a and FO/m for the (2) new FO entities.  (ASIDE:  utilizing these country prefixes did not seem to cause any problems upon import of my qsodata.db into DXB2000.)

    Third, now you may copy the (3) updated .db files into your Dxbase directory.

    The updating of these .db files is a work in progress (not to be confused with a FCC WIP -:) ).  I acknowledge that I likely have some tweaking to do on some of the FO operations that have taken place recently, and for which the same call was used from both FO/a and FO/m.  Further, as I also like to contest, I have worked a fair number of tech+ KC6xxx's and KG4xxx's on 10m of late.  Unless they are entered in the full mapping database, they have a tendency to get imported from my contest logs into dxbase for DOS as a KC6 or KG4, respectively.  Once I have done some additional tweaking, I next hope to turn my attention to DXB2000 and determining if updating globally is viable.

    Accordingly, I will be very QRV for information on any of the FO operations, as well as the full callsigns of any KC6xxx's or KG4xxx's you may encounter.  The KG4xxx's are particularly interesting to me as you can likely surmise from my other call noted below.

    Last, I welcome your suggestions and input.

73 & CU on the bands de Doug W4OX / KG4OX.