I've been doing a little thinking tonight (hopefully the resultant smoke wasn't a hazard to navigation). I have a couple more suggestions I'd like to add to the ever-growing wish list.
. Expand the QSL VIA field to include OQRS (Online QSL Request System) that's now starting to take hold of larger DXpeditions. In this case, no outbound card is sent. . Change around the mappings situation so that there's an actual database field for QSL Manager associated with each individual QSO. I think this may be a little simpler overall, especially for situations like 3V8BB, which has had many different operators throughout the year with different QSL routes, despite the same call. It may also make populating the manager's field on the label/card a little more intuitive. . This is a big one for me: have a separate column for the QSX (as it's data I'd like to include in labels). If this ever happens, I'd love to have a means to look into the NOTES field for any string that's formatted xxxx.yy or xxxxx.yy and move that value from the NOTES field into the new QSX field. Failing that, perhaps just have the filter and populate one of the SPECIAL fields which I could rename on a label. ----------------------------------- Regards, Peter, W2IRT
______________________________________________________________ Dxbase mailing list Home: http://mailman.qth.net/mailman/listinfo/dxbase 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
