[Dx4win] setting QSL manager to "blank"

Mel [email protected]
Tue, 24 Feb 2004 05:45:56 -0500


Re Frequency. It's one of the things he's pretty stubborn about... That =
and
no structure for Notes... Ie name and qth...

Because of that and the weak support for LOTW I finally gave up and =
bought
another product. For the time being, I'm still keeping DX4Win current in =
the
hopes Paul will finally come around... But I'm starting to doubt it ;-)


> -----Original Message-----
> From: [email protected]=20
> [mailto:[email protected]] On Behalf Of Zoran Brlecic
> Sent: February 23, 2004 23:22
> To: [email protected]
> Subject: Re: [Dx4win] setting QSL manager to "blank"
>=20
>=20
> Jim Reisert AD1C wrote:
>=20
> >1.  The data is NOT stored in the log, it is stored in the=20
> country file,
> >    much like the prefix data.  Therefore, there is no way=20
> to permanently
> >    associate a QSL manager with a particular QSO. This=20
> means you can not
> >    assign a QSL manager on a QSO-by-QSO basis.
> >
> This is really no big deal. If you want to change the old manager=20
> assignment to "none", there is a way to fake it: simply type=20
> in a period=20
> (.) in the manager field. The assignment will change and the QSL card=20
> printout will show a dot. Good enough.
>=20
> >2.  Once a station has a manager, all subsequent QSOs with that same
> >    station will also inherit the most recent manager.  There is no
> >    expiration date for managers, like there is for DX prefixes.
> >    Thus, there is no way to set a manager to "NONE" except to delete
> >    the manager record completely, which invalidates all QSOs, even
> >    those that *do* use the manager.
> >
> The only drawback to the separate manager db system, as far as I can=20
> see, is when a station has two or more managers at the same=20
> time, like=20
> K1B had, for example (one for CW and one for SSB). Even then,=20
> this will=20
> only affect the log database if the QSOs are made on the same day. If=20
>  they're not (CW QSOs on one date and SSB QSOs on another),=20
> the system=20
> handles it OK. This happens so rarely that I don't find it a=20
> big enough=20
> reason to mess with the log database structure.
>=20
> >[snip] In summary, the way the QSL manager field works is a=20
> limitation=20
> >of DX4WIN.
> >Paul will have to change this to support the features people want.
> > =20
> >
> And now for my usual mantra: I would really like to see the actual=20
> frequency entry instead of just the band. I figure if I=20
> repeat it enough=20
> times, Paul will do it just to shut me up.
>=20
>=20
> 73 ... WA7AA
>=20
> _______________________________________________
> Dx4win mailing list
> [email protected] http://mailman.qth.net/mailman/listinfo/dx4win
>=20