Access Backup Template
Backup Access

MS Article: DoCmd.Save method (Access)

Maybe something similar to

var app = GetApp();
app.DoCmd.RunCommand(AcCommand.acCmdCompileAndSaveAllModules);

AcCommand.acCmdSaveAllModules

Many thanks!

It will take some studying, but i rather enjoy learning. Only issue with me is that when i do learn, it just doesn't stick around too long (in the event you also understand Star Trek references, and i am almost exclusively TOS, "Spock's Brain").

What are you actually wanting to save?

Honestly i simply want to make sure the entire DB is saved, not a specific form nor other object. I had reviewed the DoCmd.Save page you referenced prior to pestering the good folks here, but it specifically stated that it saves the active object. That could mean one form, as opposed to everything that may have happened across a session. It is possible that my paranoia stems from Excel, as there Save saves everything and not saving can mean losing everything, whereas it would seem in Access much gets saved as one moves along.

Many thanks-

Is this only for you when you are developing the db, not for when you are using the db?

Thank you Alex,
it would more be for when i am developing.

When in use there are sometimes multiple "daisy-chained" forms that build upon one another. Each of them when exited, whether to the next logical form or back to the previous form, has (i really like to think) a built in save, so i think i am pretty well protected there.

I just don't know specifics while i am developing, so every time i have multiple objects open in design view and am over coding in the VBE, i will click the Save in the VBE then before closing any of the forms save each of them and then when they are all closed i will hit "Ctrl-S" and sometimes even after that save a backup! I get the feeling i am going into serious overkill due to my lack of knowledge... :)

Thanks for hanging in here with me, i appreciate it-

So if you've developing the forms then you wouldn't be using code to save the WIP as your Form would be in Design View so you can't click any buttons
Unless I'm missing something

(You could call functions from the immediate window)

No you probably are not, i probably am. Juggling a bit too much with this, my normal work, and an upcoming move (wish it was back to FL, but Virginia Beach might do for a while).

With the user experience: Am i safe to say when exiting (Quit), prior to the quit if a DoCmd.Save is run, if anything was not saved in the normal course of thing it will be saved then?

With development: If i do a Ctrl-S are there any aspects that won't save that i might have hanging open and not individually saved, and if there are, is there a "global" any-stuff-that-isn't-saved-will-be-saved command?

I think that sums everything up. Simple paranoia of not doing it right-

You know, some movers are real scum...

User experience is it only changes to the data that you're worried about losing?

Frankly, paranoid.

I guess it all stems from those Lotus and early Excel days when one could close out what they were working on, or there could be an interruption of power, and lose anything that had been done in the meantime. Then was the time, hazy in memory, when MS decided to automatically implement xlsx as the default save. I had done a lot of work, just went ahead and saved it, closed out, and when i came back all the code was gone. Obviously i went back to the prior and figured out what was happening, but that gave me that punched-in-the-gut feeling. I have almost certainly over-labored this thread which wouldn't be the case if i had more experience working with Access. Best to let this go with my thanks to all, and if something happens i will simply swear a bunch but quietly so no one can hear me, fix it, and learn-

Many thanks,
-Bruce