I would be glad to export all my qsling tasks to another set of software if it could do a better job of maintaining accurate qsl managers and optimize the qsling tasks, but I do not know of another package that is better than DX4WIN.
I have posted several messages in the past suggesting that it would be nice to simply know where the qsl address came from (and mainting more than one qsl manager in some cases) and color code it differently if it came with the program, was imported, from the CD Rom Database, Go-list, off the spot window, etc. In reality, QSL managers (and qsling in general) far outweigh the cost of the DX4WIN program and it may require (or there may exist) a program that can access several databases and give you this information in a format that DX4WIN can use since the author has never actually provided qsl information, although a host of volunteers have and continue to provide this information. It is a tremendous job as John from the Go-list can attest. I just simply gave up. I put in the entire database provided by ON4AOI's wonderful web site, on top of my own database, and keep putting in VLADs updates as they are quite current for both qsl managers and qsl managers addresses and reflect 425DX information which is also very carefully researched and maintained. You still get errors this way, but without an ACCURATE time tag on each and every qsl manager and someone striving to keep them current, I have not found a better way. I then use the go-list to double check all direct qsls and all critical bureau qsls, but this is a slow way of cross checking. Any other suggestions would be appreciated. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Larry Benko Sent: Tuesday, April 23, 2002 6:27 PM To: dx4win@mailman.qth.net Subject: [Dx4win] QSL manager updates I just spent the past several hours messing with the QSL manager updates provided graciously by Vlad, UA6JD. I don't know if everyone except me is aware of a small shortcoming in the update process but here is what I found with DX4WIN ver. 5.03. Callsign HC8N had AA5BT for a qsl manager but now has W5UE. If the original QSL manager database has the field "HC8N,,AA5BT", then importing the field "HC8N,,W5UE" will not override the original QSL manager. However if the imported field was "HC8N,23/04/2002,W5UE" then both the early QSL manager and the current QSL manager show in the database. I would rather have both managers in the database for obvious reasons such as outstanding QSL cards that may have been sent to the old QSL manager. It appears as if a blank in the effective date field is treated as the earliest possible date and importing another QSL manager again with the earliest possible date causes the import algorithm not to override the original manager. Am I missing something here? 73, Larry Benko, W0QE _______________________________________________ Dx4win mailing list Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win
