Get out the ol' pen... Eric Rosenberg wrote: > I've received two conflicting answers. > As to the comment: "You don't really need a name on a QSL card... and it > gets meaningless if you do a lot of contesting where the ops name is > often unknown." I agree in the contest context. However, this was a > special event station and it would be a nice touch! > > Eric W3DQ > Washington, DC / > / > > Mel wrote: >> Unfortunately the import is correct and I don't think you can do >> anything about it. >> >> Comments refer to a specific QSO. >> >> Notes apply to the callsign. This is where the name normally goes. >> >> This is how it works in all the logging programs I am familiar with. >> >> You don't really need a name on a QSL card... and it gets meaningless >> if you do a lot of contesting where the ops name is often unknown. >> >> Eric Rosenberg wrote: >>> I have an ADIF field <comment> that has the operator's name and >>> callsign. It is imported into DX4Win as NOTES FOR THIS QSO. >>> >>> In order to print that data on a label using the && command, that >>> data needs to be in the NOTES FOR THIS CALLSIGN field. >>> >>> DX4Win doesn't recognize the ADIF <NOTES> field... I just tried it. >>> I don't know of a way to change NOTES FOR THIS QSO to >>> NOTES FOR THIS CALLSIGN so I can use the && parameter when printing >>> the labels. >>> >>> Any help is appreciated. >>> >>> 73, Eric W3DQ >>> Washington, DC >>> _________________________ >> > ______________________________________________________________ Dx4win mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[email protected]
This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
