Multiple Saves with One Action

marpler

Because of the importance of my Quicken file, I routinely save a backup file now x 4. In case of unfamiliarity, here are my key sequences: At the Quicken main register type CTRL-B to the backup process, select the prior used file place and name by selecting the downward arrow showing the backup file list, add date to file name if needed, select Save. Repeat the process multiple times.

I save one backup on several internal discs, one to Dropbox and one with a specific date in the file name. This requires me to do the backup sequence 3-4 times depending on how patient I am that day.

Could you come up with a process where I could save, say in sequence, all 4 files with one action?

Thank you for your consideration,

mcgearing

Would allow for multiple (at least 3) backup locations (eg.. cloud, usb, computer completed with one backup action.

BRTardiff

I've been looking for this functionality for years. Thanks for posting.

Chris_QPW

I can see how you can currently get two backups with the current system, maybe even three if you go against the recommendation of storing your main data file in a "Cloud folder".

Three for pretty much the price of one (or two if you don't store your data file in a cloud folder).

1. Store data file in cloud folder.
2. Set automatic backup location to another location, with it set to do it for every time you exit Quicken and set option to ask for a "manual backup" when you exit Quicken.
3. Exit Quicken.

Rocket J Squirrel

Write a batch (command) file as in the old DOS days, using the COPY command to make as many copies as you like.

Chris_QPW

https://community.quicken.com/discussion/comment/20445835#Comment_20445835

This is probably how I do it, if I wanted that functionality.

R DIlly

A "user exit", i.e. an option to call a batch file (or other script) passing the name (and path?) of the backup file after saving it would be a open-ended general solution for those willing to do a little coding. The file is important enough to me that I'd be inclined to store copies on several cloud servers.

Chris_QPW

@R DIlly If we aren't talking about multiple data files, this can be handled in the batch file.

User starts batch file; batch file starts Quicken and waits for it to finish. Once Quicken quits batch file copies Quicken Data file to all the places the user wants.

Example (EDITED original was for copying in and out of a "cloud folder" and also this forum editor eats the back slashes in some cases):

@echo off
set DATA_FILE=c:\Quicken\Current.qdf
set QUICKEN_DROPBOX_DIR=%USERPROFILE%\OneDrive\Documents\Quicken\
 

"%ProgramFiles(x86)%\Quicken\qw.exe" "%DATA_FILE%"

copy "%DATA_FILE%" "%QUICKEN_DROPBOX_DIR%"

IF %ERRORLEVEL% == 0 GOTO END

start /wait cmd /C "ECHO %DATA_FILE% copy of data file failed. && PAUSE"

:END

R DIlly

@Chris_QPW

Yeah, that's a good idea. I do have a couple wrapper scripts using that general idea, but no post-processing.

My preference would be to keep a copy of the dated backup files (e.g. QDATA-2024-08-03.AM09.44.QDF-backup), but that's easily done. I wish I didn't have much experience tinkering with Quicken, but several times I had to go back a week maybe to straighten out something! :-(

I believe XCOPY has options to synch only new or changed files (though I'm more of a Unix guy)…

Thanks!

Chris_QPW

Note that if you just open a data file in Quicken and exit, it will be different, so any copy option that looks for changes is going to copy every time anyways.

My best suggestion though would be to have a robust backup for your data files on your system. I can't imagine anyone that the only important file they have on their system is their Quicken data file.

Rocket J Squirrel

@Chris_QPW
User starts batch file; batch file starts Quicken and waits for it to finish. Once Quicken quits batch file copies Quicken Data file to all the places the user wants.

I don't love this idea. If something goes wrong in a QWin session, I don't want the result copied elsewhere. I run my "copy everywhere" command script manually only when I am happy with the state of the data file.

Chris_QPW

https://community.quicken.com/discussion/comment/20447457#Comment_20447457

Actually, one of the reasons I like the batch file is because it can be aborted, and as such the "post operations" don't happen.

I use such a batch file, but in bit of a different way. I actually check in my Quicken data file into a source control system (which BTW does a binary compare so that many copies don't take up very much space).

If I'm testing or if find I messed up in a Quicken session, I just kill the batch file before closing Quicken.

Note of course since you have changed your data file you do have to have a way to recover the original data file before the mistake, but that would go for any system.