[Dxbase] Import/Export Issues

[Doug McDuff]

Please let me preface my remarks by saying that Dxbase has been my 
logging program since the early DOS versions.  So, my decision to 
consider a transition to another program has not come easily.  While 
I would absolutely prefer to stay with Dxbase, there are a few key 
issues that are making it difficult.

That said, my primary issue is with the import of ADIF files from my 
contesting programs.  I (wrongly) assumed that Dxbase had been 
importing the files "as-is."  Instead, in going back through over 40K 
Q's, I learned all too well that has not been the case.  As an 
example, I just imported my contest log from the recent California 
QSO Party (CQP).  One station I worked was KE1B/6.  Unfortunately, 
when Dxbase imported the file it changed the CQ zone to 5, instead of 
3 (apparently ignoring the "/" designator).  This is just one of many 
examples I found in perusing the log.  As a consequence, I have had 
to go back to my handwritten zone data for purposes of keeping track of 5BWAZ.

With respect to other imported logs, the country has been 
changed.  In other words, it does not appear to me that Dxbase is 
following the ADIF 2 protocol.  This was confirmed when I checked my 
log after importing my CQWW RTTY file.

And as for exporting logs, the ADIF protocol  as I understand it for 
phone contacts is SSB, with no distinction as to USB or LSB.

When Jack announced his "retirement" from support of Dxbase, I 
purchased Dx4win.  While its format is still somewhat alien to me, I 
have been pleased with several of its features.  First, it correctly 
addresses the zone information.  Second, it has an updateable (is 
there such a word?) country database that is maintained by AD1C who, 
as many may already know, also maintains the contest logging program 
databases.  Third, it has the ability to edit the field order "on-the-fly."

While, I can certainly live with the field order method in Dxbase, 
the zone and country issues are beginning to stick in my craw.

I understand that these issues may be the result of cockpit error, 
and welcome any suggestions to overcome them, but if not can these 
perhaps be addressed in the next release?

Thanks for hearing me out.

73, Doug W4OX


Also, and with respect