This problem keep cropping up. It's easy to fix, but perhaps the program could be modified to prevent it from happening.
After starting DXbase after a PC lockup, it asks to "initialize tables". Usually no problem, but occasionally I get an error: "call AAxBBB has incorrect IOTA <AN200>. Correct and re-run" or something similar to this (I didn't copy word for word". This seems to be traceable to: 1. The spot came off the packet cluster. 2. It was logged from the cluster with a right mouse click. 3. There didn't appear to be an IOTA value in the cluster spot. 4. The IOTA field in DXBase appears empty. The fix is to enter ANY valid IOTA number in the record and save it. Then go back and highlight and delete the IOTA number. When this is done the initialize tables routine runs correctly and does not complain about that QSO any longer. My guess is that an "invisible" value is being written into the IOTA field when the cluster spot is logged. DXBase is correct in that the IOTA value does not exist, but you can't delete what you can't see. I guess either a change in the validation routine to prevent this would work, or I could add the value AN200 in the IOTA table. Then it could be deleted whenever this happens in the future. Not a big problem, but I had it happen on 3 spots just over the last week. Don't know if there's been a change in the cluster software (I use a local 2M RF cluster) that caused it or what. Thanks, Jim, KK1W
