I must correct myself. Using the DX4WIN.CTY that was shipped with DX4WIN 7.02 in 2006, where the Prefix for USA was "W", I did not encounter the bug.
Using the DX4WIN.CTY from 10 December 2007 (that last one before the addition of FJ), where the prefix for USA was "K", I *could* reproduce the bug in 7.02. I have not tried 7.01 yet, but will see if I have a copy at home. 73 - Jim AD1C --- Jim Reisert AD1C <[EMAIL PROTECTED]> wrote: > Hi Folks, > > I just tested DX4WIN 7.02 and did not run across the country editor bug when > adding FJ/St. Barthelemy. > > For anyone who *did* have log data corruption, were ANY of you using a > version > of DX4WIN *other than* 7.03? > > 73 - Jim AD1C -- Jim Reisert AD1C/?, <[EMAIL PROTECTED]>, http://www.ad1c.us From [EMAIL PROTECTED] Mon Jan 7 17:00:16 2008 From: [EMAIL PROTECTED] (Mike Mellinger WA0SXV) Date: Mon Jan 7 17:01:20 2008 Subject: [Dx4win] The trouble with backups Message-ID: <[EMAIL PROTECTED]> Lots of good suggestions here. Everyone is so quick to jump on the backup the data bandwagon that maybe a few comments are in order. 1. The bug that brought these problems on was subtle. Until you went back and looked at your old records you would not have known about it. Therefore frequent backup is only one issue. You have to retain the backups indefinitely since you never know how far back the bug goes. I'm lucky -- I can literally go back years for critical files. 2. DX4WIN keeps no journal file. If the log file disappears, say from operator error deleting it or something else, you will lose all data back to your last backup -- unless you kept a paper log in between backups. A more robust program would keep a journal file (maybe writing it somewhere else -- say a different disk or a network disk) that would have enough information to update from a previous backup. To be honest, I don't expect this but it would certainly provide a much higher degree of safety. 73, Mike WA0SXV
