I've been compacting and backing up my QSOLog and Ref Data .mdb files after every operating session, using flash drives and a Zip disk for storage. In fact my doing this so consstently could be taken as evidence of anal retentive behavior.
However, yesterday it paid off. My computer (or more correctly, my less than desirable Windows Me operating system) happened to crash in the middle of an initialize tables operation for Dxbase. After re-booting, bringing up Dxbase and attempting to re-initialize tables, I got the dreaded "No record found" message. I did try the "repair database" option in the Dxbase backup utility, but got the error message again. I was mighty glad I had a recent backup on a flash drive! I simply replaced the corrupt NI0C.mdb file with my backup, and manually entered the one QSO I had made since the backup. All is well! Phew! 73, Chuck NI0C From [EMAIL PROTECTED] Wed Mar 22 10:13:48 2006 From: [EMAIL PROTECTED] (Ed K1EP) Date: Wed Mar 22 10:17:34 2006 Subject: [Dxbase] Strange LoTW QSL behavior Message-ID: <[EMAIL PROTECTED]> I periodically use the Selection Wizard to create an ADIF file which I then submit to the LOTW. When you do this, there is a window that asks if you want to flag those QSOs as being sent to the LoTW. Back in January, I created an ADIF file for a 10 day period between January 20 and 30 and checked that I wanted those QSOs flagged. It had over 700 QSOs in it that I submitted to LoTW. However, only about 60% of those QSOs got flagged as being submitted. As I scan through the log, some of which took place during the CQWW 160M contest, I see some QSOs on Jan 28 being flagged and others not. Not so for the contest QSOs on Jan 29. All of them are flagged. I can't seem to correlate anything as to why certain QSOs were flagged and others not. Has anyone seen such behavior before?
