At 03:19 PM 2/17/02 -0500, you wrote: >Hi Wes, > >1. Yes, the CFM field is imported in the DXB Import. Can you imagine if it >wasn't?
Yes, and that is the problem. >2. The spots you see in refdata.mdb are some samples. If they bother you, >you can delete them by clicking in the DX Info window, Spots tab, with your >right mouse and select empty all. I tried this, didn't see any entries and using "Empty entries" I get a report that "No records found." >3. If the QSO is confirmed on one machine and not on the second, then you >must have selected the wrong database on the second machine, or you didn't >actually save the QSOs when you imported ( i.e., maybe you had the trial box >checked). Not true. I believe that the problem is thus: If a record already exists in both databases, the import may not make *any* changes to it. I'm guessing that you probably look only at a few of the parameters (those in the error log?) of the record before deciding that it is a "dupe" and make *no* changes. So as per my earlier example, JT1/K4ZW was already in both logs. In doing the import from the database with the "new" data, ie. "CFM", the record appears to be a dupe and an Error message is generated and no change was make to the target database. JT1/K4ZW remains "unconfirmed" in the target database. I just tried this experiment: 1) Set the most recent QSO record in the "source" database to confirmed. (This follows a previous import, so the "target" database has this record.) 2) "Log" a dummy qso in the source database. Set it to "CFM" 3) Import to the target database. 4) The previously existing record *is not* updated to CFM. The dummy record is imported just fine and shown as "CFM." It seems that importing is not a good way to update existing records. Right? 73, Wes
