Hi
After no less than 4 phone calls from Joe, WA6AXE (I'm talking about
superb assistance) and also great
suggestions from Art, W2NRA, it appears that there is a workaround but
no real solution to my problem.
As it stands now, to prevent DXbase from printing qsos worked under
different callsigns to a single multi-qso label,
one must assign a separate label group for each callsign.
This can be accomplished in two ways:
By using a Selection Wizard:
1. In the Selection Wizard window select a "Over ride User Option
Group Settings" check box
and assign a number or letter designator for the label group
2. Select Opr Call. check box and type your call from "Opr Call"
column found in the main Qso log window
3. Specify any other search criteria by using Qso Filters - if required
4. Run the wizard and send the labels to a new group
5. Repeat steps 2,3 and 4 for each different callsign ( "Opr Call" field)
By modifying the Labels database.
1. Select Tools --> Database Access --> Labels... and click on "Qso
Labels" tab
2. For each different callsign found under "OPRCALL" column , assign
either a single digit number or a single letter
to corresponding "GROUP" field. I suppose Access 97 could also
be used to automate things if there is a large
number of labels already found in the Labels database
Print each Label Group separately and affix the labels to their
respective QSL cards.
In reply to Art's suggestion # 1, I did attempt to use 5160-3q label
template (Avery 5160 3 qso) by adding a "OPRCALL"
variable in order to distinguish the qsos worked under different calls
from each other. What I found is that DXbase would
print the Call (from OPRCALL field) for the first QSO but second and/or
third QSO would still come from different "OPRCALL"
field regardless.
Although both techniques work, they are somehwat cumbersome for me. I
currently have 8 different calls in my database , so it would
take some time to sort all this out. Perhaps, I'll be better off by
using only single-qso labels for now.
Unless I am missing something else, the only elegant solution to this
would be for DXbase authors to implement a
enhancement in the application code and do a check for the "Opr Call"
field when printing labels. There is no reason
, IMHO, that QSOs worked under different calls should ever be printed on
the same card.
Thans again Joe and Art!
73, Nick
ve3ey
>Hi
>>
>> Is there a practical way to prevent QSOs with different "Opr Call"
>> field from printing on multi qso label?
>>
>> For example , I have a three qsos with dx1dxx and each qso comes with
>> different "Opr Call" field such as ve3xyz, ci3xyz and vg3xyz. They
>> all count for my dxcc and as such they all come from a single database
>> file.
>>
>> When I select to print all three qsos by using a multi qso label they
>> all end up on the same label. In other words Print Label Project
>> does not make a distinction between "Opr Call" field and sends them all
>> to a same label.
>>
>> Using dxb2003 here but I would like to know if this is also possible
>> with 2004 or 2005.
>
