AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Tuesday, March 01, 2016 8:20 PM
To: dxlab@...
Subject: [dxlab] Re: "Inbound OQRS" greyed out
Getting there! Everything you mentioned worked well but I still don't have full understanding of how it handles a direct request. How does DX Keeper know whether the people requesting a card via OQRS have paid for a direct mail response or are just asking for a bureau card? Does DXK differentiate that when it downloads requests and imports that data?
As is stated in
<>
the "Inbound OQRS" function will "set the logged QSO's "QSL Sent Via" item to B (for bureau) or D (for direct) as indicated in the OQRS request". When your QSO partner makes an OQRS request, he or she specifies whether a direct or "free, via the buro" response is desired.
And still one other very small problem. I have the "confirm multiple QSOs per QSL" set but there doesn't seem to be an override for different myQths. I made 3 QSOs with this test OQRS-request station, one from each of 3 different locations. Neither he nor I will really care where the Qs were made from, so long as they're from the same DXCC entity. They're even within the same circle for WAS eligibility. Is there any practical way around this or is it just easier to generate one label per QTH and stick 3 of them on the card instead of one multiple?
DXKeeper cannot be configured to ignore "my QTHs": if you've made QSOs from different locations, they will be printed on separate labels sot that your location can be accurately specified in each case. Pasting multiple labels same card is certainly reasonable.
73,
Dave, AA6YQ
