Perhaps for future such things, having DXkeeper do something like
open up a window and ask "Recompute the database now?" if it is
needed after an upgrade might safe a few of us poor lids from having
to re-ask FAQ's.
The instruction window that opened when you updated the DXCC database
to version 2.5.5 specifically stated that you would need to Recompute
in both DXKeeper and SpotCollector.
That said, Dave and I have been discussing strategies for automatically
triggering a Recompute - at least in DXKeeper - when necessary. How
and when that is implemented will be up to Dave (of course) but it will
probably be tied to comparing the DXCC Prefix list in the log database
(progress table) to the one in the current DXCC Database. Whether a
mismatch will trigger an automatic recompute with attendant flagging of
invalid subdivision entries and broken entries or only a recommendation
that the user perform a manual Recompute (which will occur every time
the log is opened until the discrepancy is resolved) has still not been
settled.
73,
... Joe, W4TV
On 3/4/2016 11:07 AM, Daniel Brown daniel.h.brown@... [dxlab] wrote:
Joe -
Thanks for the response. It does appear to have fixed the issue.
That said, I'm not sure how I could have guessed that would be the solution
for a brand new contact - when DXKeeper has seemed to be working fine. I
haven't been actively monitoring the group, recently and didn't get
anything when I searched for a few terms around "Reunion" "FR" and
Dxkeeper. Guess I should have dug a bit deeper before assuming I'd get a
friendly and helpful answer back from fellow hams. Perhaps for future such
things, having DXkeeper do something like open up a window and ask
"Recompute the database now?" if it is needed after an upgrade might safe a
few of us poor lids from having to re-ask FAQ's.
73 - Best regards.
N8YSZ.
On Fri, Mar 4, 2016 at 9:30 AM, 'Joe Subich, W4TV' lists@... [dxlab]
<dxlab@...> wrote:
Please review the dozen or more times this question has been asked
in the last few weeks.
You apparently failed to follow the instructions when you last updated
the DXCC database which called for performing a "recompute" to update
the log in DXKeeper in order to reflect the updated DXCC Prefixes.
In DXKeeper, select the "Check Progress" tab then click "Recompute"
in the center of the bottom row. Once that has been completed, you
may also want to perform a recompute in SpotCollector to update any
"old" spots in the Spots database. In SpotCollector, select Config ->
Spot Database and click the Recompute button in the middle of the
right column.
73,
... Joe, W4TV
On 3/4/2016 8:35 AM, Daniel Brown daniel.h.brown@... [dxlab] wrote:
Greetings -
I worked FR1GV the other day on JT65 (yay) but am having trouble
getting it logged with DXKeeper. I keep getting a message that says it
cannot be logged because the QSO contains invalid items. The "DXCC"
field is flashing red when "FR" is selected. FR was automatically
filled by DXKeeper, upon entering the call sign. I changed it to FR-G
(which obviously isn't correct) and of course got an error back from
LOTW when the contact was confirmed.
Any thoughts here?
73, N8YSZ.
