-----Original Message-----AA6YQ comments below
From: email@example.com [mailto:firstname.lastname@example.org] On Behalf Of
Sent: Monday, July 16, 2012 9:13 AM
Subject: [dxlab] Re: DXKeeper 10.3.2 is available
Hi Dave -
Thanks for spending the time on this. Since it only impacts people who have
more than one log and use WorkSpaces, it might not be worth the effort to
resolve this - especially if it's pilot error. However, please give me one
When I finish working on one log, and if I make a change to something - like
the log layout, I'll save the change, and then Update the WS.
terminate that application before directing the Launcher to update theAfter making a change in a DXLab application's setting, you must
When I activate a different WS and open that log, the backup location is
that of the previously updated WS. It seems like the backup directory for
the WS that was just updated is overwriting the backup directory for another
callsign/log. I have multiple folders within my backup directory (one per
call). Updating the WS changes the backup file location in ALL of the
folders - not just the for the call that is being updated.
the files in each of two of your Workspace folders. Now direct the LauncherUse Windows Explorer to view the "date and time of last modification" for
to Update one of these two Workspaces. Check the "date and time of last
modification" of the files in each Workspace folder. Were both Workspaces
updated, or just one?