Hal, The group numbers work out very well for me. As said, I do maintain all my DXpedition calls and PG5M contests in a single log, but using the group numbers to identify the respective call/contest. Now with incoming QSL's, I just type in the call and get all QSO's listed that I worked, regardless the DX-call or contest. Next I can confirm the respective QSO's. A the time of printing, I let the program also print the group number at the bottom of the label (this is a tick box in the QSL printing menu). Now all QSL labels come with the call associated with the group number. Example: "You worked 3D2GM" or "You worked PG5M CQWWCW". With all the sheets with labels in front of me, I peel off the label and can see on what QSL card I have to stick the label.
The benefit of this process is that you don't need to run label printing for each call sign. Especially when people send me QSL requests for different call signs, I can confirm in one go, instead of opening different logs/databases to check the different calls. Regards, Gerben - PG5M -----Original Message----- From: Hal Kennedy [mailto:hal...@comcast.net] Sent: woensdag 21 augustus 2013 16:41 To: Gerben A.Menting - PG5M Cc: dx4win@mailman.qth.net Subject: Re: [Dx4win] Log for second callsign Thanks Gerban, I have gotten this far. I cant seem to label groups 1 and 2, but as long as they are numbered I can always figure that out later. As a stand along long, I found it troubling that the callsign in "preferences" was not the old callsign but locked down to the new one. I suppose in the end this does not matter. Thanks for the help & 73 Hal N4GG & WA4BTC On 8/21/2013 10:21 AM, Gerben A.Menting - PG5M wrote: > Hal, > > To be more precise on how I handle this, do the following. > You have your current log which may be called MASTER or N4GG (whatever > name you use). > Assuming you have the other logbook already in an electronic format, > create a new log (File | New) and give it a name (you can use the call > sign for that log). Next you have to indicate the group number for the > QSO's in this log. Go File | Preferences | QSO, and fill 2 in the > Group field. I assume you have 1 for the first log. > Next import all the QSO's into this log. > > Now you can handle the 2 different logs accordingly or you can merge > the two logs. To do the latter, take the following steps: > First open the first log (MASTER or N4GG in this example). > Next: File | Import | and chose DX4WIN8 I/E and chose from the menu > File | Import. Follow the next steps to select your file with the > second log and import it. Save the log. > > Now go to the menu and chose Filter | Edit Group Names (look in the > manual how to do this) and give a name to the group numbers. In your > case 1 is N4GG and 2 is the other call. Once ready, you will have all > calls in one log but you can see for which call the QSO is (assuming > you have selected "group field" in your logbook report. > > Success, > > Gerben - PG5M > > -----Original Message----- > From: dx4win-boun...@mailman.qth.net > [mailto:dx4win-boun...@mailman.qth.net] > On Behalf Of Hal Kennedy > Sent: woensdag 21 augustus 2013 15:09 > To: dx4win@mailman.qth.net > Subject: [Dx4win] Log for second callsign > > Trying to set up a completely separate log for an old call-sign of mine. > Starting DX4WIN my call and name are already in [preferences] and > can't be changed. How can I enter a new call - same name? > > Hal > N4GG > > ______________________________________________________________ > DX4WIN mailing list > Home: http://mailman.qth.net/mailman/listinfo/dx4win > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:DX4WIN@mailman.qth.net > > This list hosted by: http://www.qsl.net Please help support this email > list: http://www.qsl.net/donate.html > > ______________________________________________________________ DX4WIN mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:DX4WIN@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
