Thanks for your follow up.? The date and time isn't relevant for dupe checking.? The dupe checking code is identical in all our contest programs (aside from contest specific details like once per band, oncer per contest, etc.), has been used unchanged for years and does not evaluate date and time for the check.
Enjoy!
73, Scott
N3FJP
Serving the Amateur Radio community with contesting and general logging software since 1997.
1 Peter 3 vs 15: Always be prepared to give an answer to everyone who asks you to give . But do this with gentleness and respect...
On Wednesday, March 12, 2025 at 12:26:12 PM EDT, Gary Mattson via groups.io <cheech88@...> wrote:
While those factors may be part of this, I am suspicous the dupe counter started over at 0000 hours.? I typed in plenty of dupe calls and saw the flags and then noticed after I worked a couple dupes again and the operator pointed it out that I was not seeing dupe flags. The event ran from March 9, 2025 from 1800Z to 0100Z March 10 (1:00PM CDT to 8:00PM CDT on March 9) spanning 2 days.? I think the program was allowing same call, same band; like POTA logging would allow same call, same park, same band, when the clock rolled over 0000. WIQP doesn't allow dupes for same call, same band for the whole period of the event at least as I see it in the rules.?
?
I did have a period? when the program lost contact with the 7300 and I restarted the radio to recover, but I do not think I was not seeing dupe flags after that. So I can not speak with certainty.? My point is if the clock can reset the dupe counter, it should not for the WIQP.
