[moneydance] Does anyone else have a problem with this user interface behavior?

[Stan]

On 4/9/2008 at 10:42 AM Edward A. Melia, C.P.A./Attorney wrote:

>I have not seen that pop up message "the backup file is newer" in a 
>long time.  What version of MD are you running?

I'm running build 606, and that may be why I can't make the popup message
appear anymore.  I don't know what version I was running the last time I
saw it.


>Under Preferences, what do you have checked on the Backup tab?  I 
>have 1) Make a backup every time you save and 2) Perform auto save 
>every 2 minutes.

I have "make daily backups" (to a separate directory) and autosave every 5
minutes.


>I attempted to open MD while MD was already open.  The computer took 
>me to the already open program; it did not open a 2nd copy.

No, it doesn't open a second instance, but it does replace the open file
with what was last saved.  For example, type "xxx" in the "memo" field of
one of the transactions and save the transaction.  Then open MD again.
There's no second instance, and it appears to simply take you to the
already-open program, but if you look at the transaction you just changed,
there's no "xxx" in the memo field.

Now, if you simply close MD and open it again, that transaction's memo
field has the "xxx" in it, but if, instead of closing MD without making any
changes, you type "ccc" in the memo field, then close and reopen MD, the
memo field has "ccc" in it.

It's not that big of a deal.  What seems to happen when you try to open MD
when it's already open is that it opens the last-saved version of the file
(no "xxx"), but nevertheless saves what you had open (with the "xxx").  So
what you see doesn't reflect recent changes (there's no "xxx").  If you
then close MD without making any changes, no saving occurs, so the data
file (with "xxx") is not overwritten.  If, however, you make changes
("ccc") and *then* close MD, the changed file (with "ccc") is saved and the
previous data file (with "xxx") is overwritten.

Not sure if any of that makes any sense, but that's how it works for me.
I'm not sure I would consider it a bug, so much as knowing how and when it
writes changed data to the disk.

But the popup message used to get me every time, and since it seems to be
gone, I guess I should withdraw my original gripe.  :-)

Stan