Re: Possible BUG with AC Log 6.9 concerning Deleting Duplicates
toggle quoted messageShow quoted text
Thanks for your e-mail. I'm sorry that you have run into trouble. There haven't been any changes to the remove duplicates function. I just double checked here and it continues to work fine.
First, try clicking Edit > Fill Fields Determined by Call, so that more of the fields that are compared have values and then try running the function.
If that doesn't correct the problem, compare two records that you believe are duplicates for these fields:
It is very likely one or more of the above fields have different values.
Thanks so much for your kind words on the software!
From: William D'Agostino via groups.io <william_dagostino@...>
To: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io>
Sent: Fri, Apr 9, 2021 8:31 am
Subject: [N3FJPSoftwareUsers] Possible BUG with AC Log 6.9 concerning Deleting Duplicates
First, AC Log is a great product and I enjoy using it.
I just upgraded to AC Log 6.9 from AC Log 6.7, and this was my first time using AC Log 6.9. I’m running a Windows 10 Dell laptop.
Yesterday, I worked approximately 50 stations using WSJT-X FT8 on 60m. Near the end of my radio session, I started getting AC Log error messages that the QSO was not “logged” into AC Log. This has occasionally happen with AC Log 6.7, and I never had an issue with importing the WSJT-X log and deleting duplicates contacts in AC Log 6.7.
I imported the WSJT-X log file into AC Log 6.9 to recover the missing QSOs and then ran the “Remove Duplicates” function. This is were the possible “bug” occurred. The AC Log did not delete the duplicates. I restarted my laptop and tried again with no success. I now have duplicate QSOs for all of my contacts from yesterday as well as another 1,000+ duplicates ranging back for several months.
As mentioned above, I was previously using AC Log 6.7 before upgrading to AC Log 6.9, and I never had a problem with deleting duplicates after importing the WSJT-X log.
Has anyone else experienced this possible bug? Does anyone have a solution?