开云体育

OK, then clicking the "Recompute" button at the bottom of the "Check
Progress" tab of DXKeeper's Main window should be sufficient.

73,

Dave, AA6YQ

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
Kurt
Arseneault
Sent: Wednesday, September 02, 2009 1:47 PM
To: dxlab@...
Subject: Re: [dxlab] DXK rejects Ukraine entries


Thanks for your prompt reply Dave, my DXCC database is 2.2.7.
Regards,
Kurt VE1TT



2009/9/2 Dave AA6YQ <aa6yq@...>

AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
Kurt
Arseneault
Sent: Wednesday, September 02, 2009 9:39 AM
To: dxlab@...
Subject: [dxlab] DXK rejects Ukraine entries


FIrst of all, I want to express my thanks to you for such a powerful

suite

of programs. I have been using DX Lab Suites for several months and love
it.
Your level of support for the software through the group is something I
have
rarely seen and you are to be commended for it.

However, I am experiencing one rather strange situation. I am unable to
enter Ukraine calls into my log. The DXCC field flashes red. The Code box
reads 288. After I exit, (delete the QSO),I get a box which reads there
"The
DXCC Progress table contains no entry for DXCC prefix UT". I examined the
DXCC database in Access and UT appears there. I have all the latest

updates

installed. Gremlins have crept in somewhere I suspect.

First, verify that you have the current version of the DXCC database

installed; on the General tab of DXKeeper's Config window, click the
"Database Info" button at the bottom. If the DXCC database version is not
2.2.7, then terminate DXKeeper (and SpotCollector, if its running), open
the
Databases tab of DXView's Config window, and click the button to upgrade
your DXCC database.

Then restart DXKeeper (if you had to terminate it to upgrade the DXCC

database), and click the Recompute button at the bottom of the Main
window's
"Check Progress" tab.

If this doesn't clear up the "no entry for DXCC prefix UT" problem,

please let me know.

73,

Dave, AA6YQ



------------------------------------

Yahoo! Groups Links

--
***Here is an Important Message for anyone who receives this email:***
If you forward this correspondence, please delete the forwarding history,
which includes my email address! It is a courtesy to me and others who may
not wish to have their email addresses sent all over the world! Erasing the
history helps prevent Spammers from mining addresses and viruses from being
propagated!



Kurt Arseneault

273 Meadow Lane,
Kentville, NS B4N 3V8
Canada

807 E 21 ST, Unit 11,
Mission, TX 78572

(956) 584-1769 (condo)
902-679-9783 (home Nova Scotia)
902-680-6230 (cell Nova Scotia)






------------------------------------

Yahoo! Groups Links



No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.339 / Virus Database: 270.13.74/2339 - Release Date: 09/02/09
05:50:00



------------------------------------

Yahoo! Groups Links

AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
Kurt
Arseneault
Sent: Wednesday, September 02, 2009 9:39 AM
To: dxlab@...
Subject: [dxlab] DXK rejects Ukraine entries


FIrst of all, I want to express my thanks to you for such a powerful suite
of programs. I have been using DX Lab Suites for several months and love
it.
Your level of support for the software through the group is something I
have
rarely seen and you are to be commended for it.

However, I am experiencing one rather strange situation. I am unable to
enter Ukraine calls into my log. The DXCC field flashes red. The Code box
reads 288. After I exit, (delete the QSO),I get a box which reads there
"The
DXCC Progress table contains no entry for DXCC prefix UT". I examined the
DXCC database in Access and UT appears there. I have all the latest

installed. Gremlins have crept in somewhere I suspect.

First, verify that you have the current version of the DXCC database

installed; on the General tab of DXKeeper's Config window, click the
"Database Info" button at the bottom. If the DXCC database version is not
2.2.7, then terminate DXKeeper (and SpotCollector, if its running), open
the
Databases tab of DXView's Config window, and click the button to upgrade
your DXCC database.

Then restart DXKeeper (if you had to terminate it to upgrade the DXCC

database), and click the Recompute button at the bottom of the Main
window's
"Check Progress" tab.

If this doesn't clear up the "no entry for DXCC prefix UT" problem,

please let me know.

73,

Dave, AA6YQ



------------------------------------

Yahoo! Groups Links

AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
Kurt
Arseneault
Sent: Wednesday, September 02, 2009 9:39 AM
To: dxlab@...
Subject: [dxlab] DXK rejects Ukraine entries


FIrst of all, I want to express my thanks to you for such a powerful suite
of programs. I have been using DX Lab Suites for several months and love
it.
Your level of support for the software through the group is something I
have
rarely seen and you are to be commended for it.

However, I am experiencing one rather strange situation. I am unable to
enter Ukraine calls into my log. The DXCC field flashes red. The Code box
reads 288. After I exit, (delete the QSO),I get a box which reads there
"The
DXCC Progress table contains no entry for DXCC prefix UT". I examined the
DXCC database in Access and UT appears there. I have all the latest updates
installed. Gremlins have crept in somewhere I suspect.

First, verify that you have the current version of the DXCC database

installed; on the General tab of DXKeeper's Config window, click the
"Database Info" button at the bottom. If the DXCC database version is not
2.2.7, then terminate DXKeeper (and SpotCollector, if its running), open
the
Databases tab of DXView's Config window, and click the button to upgrade
your DXCC database.

Then restart DXKeeper (if you had to terminate it to upgrade the DXCC

database), and click the Recompute button at the bottom of the Main
window's
"Check Progress" tab.

If this doesn't clear up the "no entry for DXCC prefix UT" problem,

please let me know.

73,

Dave, AA6YQ



------------------------------------

Yahoo! Groups Links

There have been many cases where a 3rd party has been able to take over qsl
duties for a deceased ham.
I don't know if there is an 'official procedure', for such a continuation.
But I have seen notices that a xyl or family member has turned over the logs
to a friend or club member of the deceased.

I and other QSL Manager Assoc. members took over possesion and qsl duties
when one of the big qsl managers passed a few year back.


On 9/2/2009 12:46:23 AM, Peter Jordahl (k5gm@...) wrote:

Thanks Art and Dave,
I had not thought to also mark the electronic confirmations as 'X'.
That will
be easily done and solves the problem. I have several such
QSO's; does
anyone
know whether others can QSL for an SK ham given that they have a log
showing
the QSO (I have in mind specifically 3A2GL, now SK) just as if they were
a
QSL manager?

Obviously I should have kept more up-to-date with my QSLs!

73
Pete K5GM

On Wed, 02 Sep 2009 01:42 +0000, "aa6yq" <aa6yq@...> wrote:

I believe the current implementation to be correct: if you are so
certain
that a QSL will never be confirmed that you don't

want it counted as

"worked" in your DXCC award progress, then set both "QSL Rcvd" and

"LotW

QSL Rcvd" to 'X' as Art suggests below; if you no longer wanted

it

counted towards your WAZ award progress, then also set "eQSL QSL Rcvd"

to

'X'.

If you've written off a QSO in this way, I don't see the point of
highlighting its existence in award progress displays and reports.

73,

Dave, AA6YQ

And I have been trying to import the w4ijy.mdb file to my Access 2007 for further analysis specific to my needs. When accessing the w4ijy file I am queryed for the password. Is the password the developer's use only?

Thanks Art and Dave,
I had not thought to also mark the electronic confirmations as 'X'.
That will
be easily done and solves the problem. I have several such
QSO's; does
anyone
know whether others can QSL for an SK ham given that they have a log
showing
the QSO (I have in mind specifically 3A2GL, now SK) just as if they were
a
QSL manager?

Obviously I should have kept more up-to-date with my QSLs!

73
Pete K5GM

On Wed, 02 Sep 2009 01:42 +0000, "aa6yq" <aa6yq@...> wrote:

I believe the current implementation to be correct: if you are so certain
that a QSL will never be confirmed that you don't

want it counted as

"worked" in your DXCC award progress, then set both "QSL Rcvd" and

"LotW

QSL Rcvd" to 'X' as Art suggests below; if you no longer wanted

it

counted towards your WAZ award progress, then also set "eQSL QSL Rcvd"

to

'X'.

If you've written off a QSO in this way, I don't see the point of
highlighting its existence in award progress displays and reports.

73,

Dave, AA6YQ

Hi Pete,

If you mark both QSL Rcvd and LotW QSL Rcvd to X then it won't appear
in DXView as W. For if both are not marked X, you haven't truly given
up on the QSL.

I do like your idea of X showing in DXView if only one is marked X.
However I have a feeling that would be a major undertaking. Perhaps
adding it as a feature request for when Dave has more time to
implement it.

73 Art W2NRA
"Keep to the Code!"
w2nra.com

On Sep 1, 2009, at 6:41 PM, Peter Jordahl <k5gm@...> wrote:

Dave,
I would like to suggest that if an entity (or band-entity) is
represented only by a QSO or QSO's that have been marked 'X'
in the QSL-RCVD box then the 'W' in the DXVIEW status listing
should be either removed or changed to an 'X'.

Yes, the contact was made, but hope of obtaining a QSL has
now evaporated. Perhaps for that reason an 'X' in the status
table would be preferable to showing a blank. The 'X' would
be replaced with a 'W' when another, non-expired, QSO was
made with that band-entity.

In my case I had a 1978 40M QSO with ZD8HR (later N6HR) which
resulted in a 'W' in the status view. He passed away in
2007 before I really started "data-mining" my log. I
just inserted an 'X' in the QSL box but the 'W' persists.

Obviously if one inserted hundreds of 'X's at one time
it could cause a major subsequent but short-lived
slowdown in DXKeeper,but I doubt that that happens.

Thanks and 73
Pete K5GM
Pete Jordahl, K5GM
k5gm@...



------------------------------------

Yahoo! Groups Links

Dave,
I would like to suggest that if an entity (or band-entity) is
represented only by a QSO or QSO's that have been marked 'X'
in the QSL-RCVD box then the 'W' in the DXVIEW status listing
should be either removed or changed to an 'X'.

Yes, the contact was made, but hope of obtaining a QSL has
now evaporated. Perhaps for that reason an 'X' in the status
table would be preferable to showing a blank. The 'X' would
be replaced with a 'W' when another, non-expired, QSO was
made with that band-entity.

In my case I had a 1978 40M QSO with ZD8HR (later N6HR) which
resulted in a 'W' in the status view. He passed away in
2007 before I really started "data-mining" my log. I
just inserted an 'X' in the QSL box but the 'W' persists.

Obviously if one inserted hundreds of 'X's at one time
it could cause a major subsequent but short-lived
slowdown in DXKeeper,but I doubt that that happens.

Thanks and 73
Pete K5GM
Pete Jordahl, K5GM
k5gm@...



------------------------------------

Yahoo! Groups Links