Exit without saving
I often find I would like to Exit Moneydance without saving the latest session (eg. if I have had 'finger trouble' - and perhaps not immediately realised it until I spotted its effect in another account or in a wrong time period, or perhaps had a 'silver moment', think I have entered a transaction but cannot see it anywhere & then not be sure whether I entered it wrongly & can't see it or didn't enter it at all). When this happens, for safety's sake I go back the previous session and start again. To be able to simply quit the job without saving and restarting would be simpler & less error prone than recalling the last but one backup before restarting the session. Further, the current method (make a mistake - close with forced save -restore last backup but one - re-do the incorrect session - close with forced save) leaves a corrupted file image in one's backup chain, unless you remember to delete it, which could, later, be used by mistake.
Please could you include a Quit Without Saving option in the FIle dropdown, protected by as many 'Are you really sure?' messages as you feel are necessary. Regards, RIck
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by -Kevin N. on Oct 19, 2017 @ 05:05 PM
Hi Rick,
The 'Save the Changes?' prompt was removed from Moneydance starting with MD 2012.
If I remember correctly, the reasoning from support was that closing the program without saving the changes could cause a loss of data when using the mobile app.
IMO, elevating the importance of the mobile app's functionality over the functionality of the main program was a misstep. It remains the number one reason as to why I still use MD 2011 for my day-to-day finances.
I think it unlikely that the 'Save the Changes?' prompt will be making it's return any time soon or at all.
-Kevin N. (not a member of MD support)
2 Posted by rickjviv on Oct 19, 2017 @ 07:47 PM
Hi Kevin
Thanks for the positive feedback.
My understanding is the same as yours. However, my suggestion is that the default action from File | Exit, & from clicking the x-box, remains ‘exit & save’ but that there is another option on the File dropdown ‘Quit & Do not Save’ protected by ‘Are you Sure’ response(s) which ought to provide more than enough protection for mobile users. The ‘quit & do not save’ could even be a hidden hotkey sequence or a separate dedicated dropdown. The programing effort would be minimal
I fear your prediction may be right but I will continue to pursue it until there seems to be no hope.
Regards, Rick
3 Posted by -Kevin N. on Oct 19, 2017 @ 08:15 PM
Hi Rick,
Force quitting the program, although drastic, was an option with MD 2012 and MD 2014 as those versions saved on close.
However, MD 2017 uses an automatic save function that saves every several moments which negates the effect of force quitting.
With the automatic save function in place, I don't really see that there is a means any more of quitting without saving.
-Kevin N.
4 Posted by dwg on Oct 19, 2017 @ 09:17 PM
There is another view of automatic saving of data.
Financial data is extremely important so maximum protection of this data should be a priority, if the data is only saved on exist or when a specific save function is executed in can place the data at risk.
Imagine if you have been working in Moneydance for a couple of hours, now may people just do not periodically save their work, now if you have a power failure for instance you could lose all the work, not all that many people have a UPS on their desktops for example. Automatic saving is a way that the software can minimize such a risk.
You can argue both sides of the case :) There are solutions that can resolve both but I believe not realistic in a $50 piece of software.
5 Posted by -Kevin N. on Oct 19, 2017 @ 09:45 PM
Hi Des,
I think MD 2011 and earlier made a copy of the existing data file when it was opened and overwrote it with the changed data file when you OK'ed the 'Save the Changes' prompt.
It seems like this may be a viable option with auto-save so as to be able to not save the changes.
Anyone who works for hours on any data file without saving it periodically deserves whatever turmoil they run into. IMHO. :)
-Kevin N.
6 Posted by dwg on Oct 19, 2017 @ 10:11 PM
Hi Kevin
The checkpoint files in MD 2012 & 2014 were in a sense these type of files, but as you know you no longer have a single file with MD2017 so it makes that type of implementation a problem, how to handle attachments also needs to be considered.
There has never been a way to go back to an older version of the data and remove any added attachments without using a restore from a backup function and as I understand it on MD2017 that removes any replication setup.
I've met many a person over the years that got exactly what they deserved :) Funnily enough many of them felt they did nothing wrong and the software should have protected them so it wasn't their fault. I had to deal with enough of them when I was a system manager
System closed this discussion on Jan 18, 2018 @ 10:20 PM.