Dave Bernstein <dhb@...>
To ensure its ability to perform callsign lookups, DXKeeper will from
now on include a copy of the DXCC database previously only packaged
with DXView. During startup, DXKeeper will determine whether DXView
is installed. If so, it will reference DXView's copy of this
database, ignoring its own copy -- this permits a single point of
database maintenance, e.g. when adding a new DXCC entity. If DXView
is not installed, then DXView will refer to its own copy of the
Callsign lookups during import operations will directly reference a
DXCC database, either DXView's (if installed) or DXKeeper's. DXView
itself will not participate in import operations, which should speed
things up quite a bit.
For callsign lookups during interactive operations (such as logging a
QSO), DXKeeper will attempt the callsign lookup via DXView if its
running; in performing this lookup, DXView updates its information
display. If DXView is not running, then DXKeeper will perform the
lookup using its copy of the database.
So import operations run fast and don't depend on (or overload)
DXView, interactive operations use DXView if its running, but in no
case will DXKeeper create a QSO that's missing DXCC prefix or country
There's more complexity here than I'd like, but most of it is hidden
from the user. If you've installed DXView, then you can use it to
maintain your DXCC database and DXKeeper will automatically be
consistent. If you aren't using DXView, then DXKeeper has its own
DXCC database (though you lack a tool to update it, and thus have to
download updates from DXKeeper web site).
The above approach is implemented (in DXView 1.1.5) and appears to
work, but I'd like to test a few more cases before posting it.
--- In dxlab@y..., "Dave, AA6YQ" <dhb@m...> wrote:
Sounds like there's a latent defect in the DDE connection betweenDXKeeper
and DXLab. I suggest you hold off until I release a version of ofDXKeeper
that performs the country code lookup without consulting DXView.Shouldn't
take too long...Service.