Along with the DXCC database support described below, this release
also includes updated online help, which is accessible via http://www.qsl.net/dxkeeper/Help/index.htm
If you've installed DXKeeper 1.1.1 or later, you can upgrade to
version 1.1.5 by downloading and then running
www.qsl.net/dxkeeper/DXKeeper115Update.exe -- your online help will
automatically be update by this process.
--- In dxlab@y..., "Dave Bernstein" <dhb@m...> wrote:
To ensure its ability to perform callsign lookups, DXKeeper will
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
things up quite a bit.
For callsign lookups during interactive operations (such as logging
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
There's more complexity here than I'd like, but most of it is
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
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 between DXKeeper
and DXLab. I suggest you hold off until I release a version of of DXKeeper
that performs the country code lookup without consulting DXView. Shouldn't
take too long...
From: Richard B Drake [mailto:rich@w...]
Sent: Wednesday, March 21, 2001 17:50 PM
Subject: RE: [dxlab] Re: Progress window
> Does this explain the large variance in confirmed countries
> mentioned earlier?
I don't know, but I am having a great deal of difficulty with
import. I took out all the DXCC entries in the ADIF file to
a lookup in DXView. It starts off going OK, pretty slow but I
live with that. Then it suddenly seems to lose communication
DXView and starts flying along without putting in a DXCC prefix.
The first time I tried it, it only put in about 10 prefixes
that happened. I tried again and this time it got to about 400
before it lost the connection. In any case it will not handle my
5000 entry log in one go. It gets up to QSO# 3762 and dies. I
handle that by doing it in two pieces but I don't know what to
about the loss of communication with DXView.Service.
73, Rich - W3ZJ
Yahoo! Groups Sponsor
iWin.com - The Place to Win Stuff!
To unsubscribe from this group, send an email to:
Your use of Yahoo! Groups is subject to the Yahoo! Terms of