[Dxbase] New features

[Gene Shablygin]

Peter Dougherty wrote:
> Hi Eugene,
> The way you've described it, my suggestion would be to have one master log
> called Eugene.MDB (or something that identifies you personall); it would
> contain a sub-log for your US station and another for RA3AA. These two
> belong under the same master since they're both your own personal
> operations. If you ever go on a DXpedition or vacation using another call,
> these logs would each have their own separate sub-log under W3UA. You could
> also have sub-logs if you activated an IOTA or US County and wanted to keep
> those Q's separate yet easily accessible. Then I would set up a separate
> master log for your club and another for your friend.

Right now I have separate logs for all callsigns used. I do not see any 
benefits of combining my W3UA and RA3AA logs, since for most of the 
awards (except USA-CA) the QSOs can't be combined (that's why I have 2 
separate 5 band DXCC, challenge and other plaques -- one for each QTH). 
Logging mobile QSOs is another challenge -- especially if you upload 
them to LOTW. Many people don't care, but if you carefully check the 
LOTW system, it keeps track of the county where you were while making a 
QSO. So if you do mobile, and want to be 100% precise, you should create 
3076 separate QTHs for LOTW uploads. It has nothing to do with DXBase, 
but I wanted to mention it here, just to show that there is no 'easy' 
solution to multiple call/qth/op problem, if you go deep into details. 
And individual mileage may vary.

> 
> I absolutely agree with the ability to properly use the OPRCALL field to
> actually log the operator who made the Q. Unfortunately that field was/is
> how the program was licensed, and one of the big changes I sure hope comes
> about in the 2010 release. Before I realized what had happened I experienced
> no end of hell with my club's log a few years ago.

I raised this problem with the previous owner of the DXbase -- but 
instead of understanding I've got a response that it is the way it 
should be, end of talk... He probably was unaware of existence of club 
stations and multi-op operations. I hope that Neal will support our need 
of keeping track of the operators, and change to the licensing model 
based on station call signs. I would have no objections (for licensing 
purposes), to have a limited number of 'master' databases per license, 
and each database associated with a particular call sign. But I want to 
be free to add as many ops to my log, as feasible. If a young boy scout 
decides to make his first ever QSO at my station, using either my or 
club call, I want him to feel as welcomed as any old timer, and have his 
name (in lieu of his callsign) be permanently recorded, without the need 
to get a new registration file from the DXBase tech support. The same 
time, if somebody uses my station with his own callsign, it is his 
responsibility to log the QSOs, and he is free to use his own logger.

But, at the end of the day, it is not the most urgently needed feature, 
so I can easily wait till DXBase 2011 or 2012, where it will be 
implemented. At least it will be another reason to keep upgrading.

> 
> -----------------------------------
> 
> Regards,
> 
> Peter,
> W2IRT
> 
> 
>