[Dx4win] Separate logs and merge

[Hal Kennedy]

Thanks Mel and also Costos for some interesting and thought provoking 
info.  BTW, thanks to Jim, the answer to the question was/is, you have 
to be in "Expert" mode to get groups to work..
73,
Hal N4GG


> Hi Hal,
>
> I have to argue a bit against Jim.
>
> I selected DX4WIN for at the time being the only log-program that 
> could handle several callsigns through the group feature. I was and 
> still am the QSL manager for SK0HS, a scout station that changes QTHs 
> and callsigns.
>
> We started with special JOTA -calls e.g SM5XAC, SM0XAC, SK0XAC. All of 
> these are easy to separate by date.
>
> Then we became a formal clubstation; SK0HS. We were and still are 
> active not only in JOTA but from different camps in different 
> districts within Sweden and we could thus use calls like SK0HS/0 and 
> SK0HS/5. We could in one year be active from 2-4 different locations 
> within the 0 and 5th districts so I used the group feature to separate 
> them; one group for each QTH and callsign, e.g.  SK0HS/5 from Vassaro 
> EU084 and SK0HS/5 Hed, i.e. mainland Sweden. I could now use the 
> filter feature to combine all SK0HS/5 QTHs to examine the DXCC status 
> for all  QTHs within the 5th-district or look at the whole data set by 
> selecting All QSOs as filter. To use filters is also possible in the 
> example Jim gave with his novice call too, however by using groups and 
> filter it will be possible to separate calls even if they are not used 
> in sequence. So, if just two callsigns are used and they are separated 
> in time with one before the other then it may be easier to separate 
> them with a time filter as Jim suggest but if not I will recommend the 
> group feature.
>
> 73 de Mel – SM0MPV
> 8S0C – Contest Call
>
>
>
> 2013/8/29 Jim Reisert AD1C <jjreisert at alum.mit.edu 
> <mailto:jjreisert at alum.mit.edu>>
>
>     On Wed, Aug 28, 2013 at 4:43 PM, Hal Kennedy N4GG wrote:
>
>     > I have created an N4GG log, group 0.  And an older WA4BTC log,
>     separate in
>     > every way, group 1.
>     > First, I would like to name or define group 0 as N4GG and group
>     1 as WA4BTC.
>
>     Hal, I'm not trying to single you out, but I'm not sure why anyone
>     needs group #s for multiple callsigns (from the same QTH) in a single
>     log, if there is no overlap by date.  For example, I have WN1UHA,
>     WA1UHA and AD1C QSOs my log.  I do not use group numbers to separate
>     them.  I created three Selections by date that cover the date ranges
>     these calls were used.
>
>     If I want DXCC status that covers the whole log, I do nothing special.
>     If I want DXCC status for, say, WN1UHA, then I choose the "WN1UHA"
>     by-date selection.  I can always use an F8 search with a date range
>     (over the whole log) if I want to find something particular, and I
>     don't feel like using a group selection.
>
>     What am I missing, other than the case where I may have made QSOs as
>     WA1UHA in the morning, then as AD1C in the afternoon after my license
>     arrived in the mail?  Why do people unnecessarily want to assign group
>     #s to callsigns?  How would I then identify just Novice Roundup QSOs I
>     made as WN1UHA, because if I create a new group number for them
>     (that's different from the WN1UHA group #), then those QSOs will no
>     longer show up in my WN1UHA "group".
>
>     73 - Jim AD1C
>