Closing a database but not the Access Application

[peterFisp]

Having gotten interested in closing Access from a form, I got the following code working:

    DoCmd.Quit acQuitSaveAll
''     Access.Quit            '  this also quits the application after saving any mods  I cannot see any difference
''       DoCmd.Quit                 ''' all of these variations will quit the application as well 

In each case, any edits are saved automatically, and then the Application closes alright.

Is there code that I can run to only close the open database, but not Access?

[June7]

Manually closing a database causes Access to set focus on File>New menu item. Access is not like Excel where single application frame can open multiple files. An Access database is basically an application unto itself. Each must have its own Access shell (rather more like Word where each doc has its own shell, but a doc can be closed and leave a blank display, doesn't automatically shift to File>New). I've never seen code that will close a db and set the Access frame on File>New.

[peterFisp]

OK, I just have to accept that. However, when I open Access from the task bar it does not display any database, only the Getting Started stuff. So I presumed it should be possible to replicate that outcome just as it's done first up.

[ssanfu]

The VBA command would be "DoCmd.CloseDatabase" (see Help)..... but I don't know why you would ever want to use this unless maybe you were using VB/C/C# automation.


BTW, using the acQuitSaveAll parameter doesn't do what you think it does. When closing/quitting Access, the DATA is automatically saved.
The parameter acQuitSaveAll saves changes to the DESIGN of the data base. If you used VBA to open a form in design view and added a control, you have the choice (acQuitPrompt) to save the changes to the form of discarding the changes.

[June7]

Okay, that did go to File>New. I also don't see any benefit. Not finding a DoCmd method to open a new or recent db into this same frame, unless it's buried somewhere in DoMenuItem.

DoCmd.RunCommand acCmdOpenDatabase appears to be a deadend.

Everything I see involves closing one shell and opening another.

[peterFisp]

Thanks, Steve.
Beautiful, that does it; I just wanted to see if it can be done. And actually I did not think the former and had observed the latter. I have used Access for very long time and never found it to have lost data.