I just tried the experiment of changing the date format, then creating a new qsl manager file in 603. Also tried closing dx4win and restarting before creating yet another qsl manager file. In all cases the qsl manager file retained the dd/mm format.
So apparently changing the date format doesn't change the qsl manager data. Wonder why yours is different. >>The QSL manager date format matches the QSO date format in your preferences. > >Both 602 and 603 have mm/dd/yy set in Preferences >but 602 has qsl.txt in mm/dd but 603 has it in dd/mm. >Guess it's controlled somewhere else. > >Oh, I just realized what's going on. >You must have your dx4win Preferences set for dd/mm. > >>There were some errors with importing QSL manager data into 6.02, the dates >>were changed wildly into the future, i.e. year 2057 and the like. There is >>no consistency to the error, so it's hard to fix them. > >There are no funny year dates in the file when I grepped it for /20. >I'd love to know what caused so many error messages unless these were needed >mm/dd changes >that dx4win would have done automatically. > >>If you suspect it's just a month/day swap, then send me your .TXT file (the >>one you exported/want to import, ZIPped of course) and I'll fix it for you. > >Thanks. I've attached the 602 file which would be imported into 603. >However it would be a lot easier for me if you just changed your Preferences >temporarily to the "stock" >dx4win mm/dd "American" style <g> and send me your updated file off list. > >Do you think if I change the date format the qsl manager information will >automatically change? >If so, I can handle the changes here which I'll have to do anyway when you >come out with 9 final. >Guess I'll experiment. > >>73 - Jim AD1C >> >>p.s. the QSL manager database that comes with 6.03 is much better, and >>Release 9 will be better still. > >We can hardly wait. > >Again my most grateful thanks. >Larry > > >Larry Alkoff N2LA Austin, TX and Daytona Beach, FL > > Larry Alkoff N2LA - Austin TX
