Hi folks,
I've run into a problem which I have no idea how to solve. Here's the
situation:
I worked H44MY for a new entity on 30M. Entered all the info I had and found
out that the QSL manager callsign I put in the log was wrong. Tried to fix it,
but although the program will allow me to en
On Sat, Sep 19, 2009 at 2:56 PM, wrote:
> I worked H44MY for a new entity on 30M. Entered all the info I had and found
> out that the QSL manager callsign I put in the log was wrong. Tried to fix
> it, but although the program will allow me to enter another callsign in the
> QSL Manager box
guard.com
http://www.uscgradio.net
http://www.comm-one.org
---
- Original Message -
From:
To:
Sent: Saturday, September 19, 2009 1:56 PM
Subject: [Dx4win] Problem with incorrect QSL manager info
> Hi fo
---------
>
> ----- Original Message -
> From:
> To:
> Sent: Saturday, September 19, 2009 1:56 PM
> Subject: [Dx4win] Problem with incorrect QSL manager info
>
>
>> Hi folks,
>>
>> I've run into a pr
On 9/20/2009 4:24 AM, Mel wrote:
> I must say I prefer the way my old logger handled this. Changing a QSL
> manager in the log automatically updated the QSL manager info by
> creating a new entry and start date.
That *is* how DX4WIN works, and is how DX4WIN has worked for all versions.
As I expl
Thanks Jim... that was the way I thought it worked... but my
misunderstanding of the problem had me convinced I was confusing it with
Logic (which works the same way). Thanks for the clarification.
Jim Reisert AD1C wrote:
> On 9/20/2009 4:24 AM, Mel wrote:
>
>> I must say I prefer the way my ol
6 matches
Mail list logo
