[Dx4win] QSL mgr maintenance and accuracy
Wendell Wyly W5FL
[email protected]
Wed, 19 Jun 2002 14:47:48 -0500
I just updated my DX4WIN qsl manager database first adding the ON4AOI update
then followed by the remaining few of the UA6JD updates. I sure appreciate
all the effort that Guy and Vlad put into searching and typing all of these
updates and making them available to the rest of us!
The UA6JD update resulted in: Added 499, Replaced 35, Skipped 200, Dupes
463, Errors 0.
First Question: I think I understand the Dupes, Errors, and the Added, but
what does the 200 skipped mean and how do I know which were skipped or
replaced, and why is replaced different than dupes? Since DX4WIN does not
show who you actually sent the card to after a qsl manager update changes
the qsl manager, sometimes I am not sure whether the card actually went the
right place a year or two later when a card never arrives.
I am sure we all strive for a perfect QSL manager database, particularly if
you do not like to waste tons of cards sent via the buro, so the accuracy of
this database is extremely important including the dates that the qsl
manager changes.
Second Question: Do others use about the same qsl manager database? I
always check and double check through the GO LIST, QSL Routes, and
Pathfinder for direct qsls, but even these databases are not perfect,
particularly if the contact is a few years old (5R8EE is a good example, but
I have many more).
Is there a better way or additional software (or databases) that makes
qsling a little easier (quicker) and more accurate for both bureau and
direct qsl's?
All suggestions sincerely appreciated.