On Sat, 6 Sep 2003 15:04:54 -0400, Mel wrote: >DX4Win doe NOT support anything other than one instance accessing the >log at a time... > >The danger is because each copy of DX4Win is actually updating it's own >memory copy of the log. When it flushes to disk... It will overwrite any >changes made to the other copy... > >Lets assume you open it in the shack... >And open it again in the office to do some QSL printing... > >And you work some new stations in the shack... Then close the log... Now >updated with new QSO's... > >When you close the copy in the office, if you update the log, you will >overwrite the Shack version... With the older version which predated the >new QSO's... > >As long as only one copy is open at a time, you are safe... But I think >it's dangerous to do it this way because a mistake can be serious... I >prefer to work with a copy of the log. If I do some SL updating, I >simply copy it back... Less chance of an error.
Thanks Mel I've learned a hard lesson. Looks like I lost 48 hours worth of QSO's because I logged in QSL's on the office computer which updated the station machine with an earlier copy. Before I just copied the n2la.dxl file over the network to the office machine but made _all_ changes on the station machine - I'll do that in the future. The only reason I did it is so spots would be updated with the latest log information. But I now see it's just too dangereous to use the station log in the office computer over the network because a single mis-step would cause the station computer to get a "stale" update. Never again! Larry Alkoff Larry Alkoff N2LA - Austin TX
