Comments on: VBA: Exit Without Saving

By: Nate

Nate — Fri, 15 Jul 2011 18:34:08 +0000

Is there any way to restart Excel within a VBA macro? I’d like to set up an error handler with a user form that allows the user to reboot Excel or continue.

By: Dennis

Dennis — Fri, 15 Jul 2011 09:29:42 +0000

Perfekt, just what I needed

By: Ken

Ken — Sun, 27 Mar 2011 01:19:27 +0000

You can also use this if you only wish to close the workbook containing the code.

Private Sub Workbook_BeforeClose(Cancel As Boolean)
Application.DisplayAlerts = False
Workbooks(“receipt tax spreader tool.XLS”).Close
Application.DisplayAlerts = True
End Sub

I used it for a calculator-type file to help me with my finances.

By: mark

mark — Mon, 24 Jan 2011 21:58:14 +0000

i just included this code in an auto open sub to create different views for different business users. (ie it will run different commands if the username is in different lists on a worksheet. (stupidly) i ran the sub with my username on the autoexit list, as part of testing. now whenever i open the file it automatically exits.

as this is a test file i cannot send it to other users as i am the only name on the list. can anyone think of a workaround for this? i need to be able to get into the macro but without it running

thanks in advance

By: A Different Scott

A Different Scott — Mon, 06 Dec 2010 16:13:59 +0000

An application I just had for this:

I had an Access VBA function open up an instance of excel, make some changes to a file in the background, and bring up a “Save As” dialog. If the user clicks “Cancel” on the dialog, it returns a value of “False”. I tested for this condition so that when the user clicks Cancel and my function eventually tries to call “ExcelAppObj.Quit” it first sets DisplayAlerts = false so that the user doesn’t receive a dialog asking if they’d like to save the changes made to the excel file.

By: Scott

Scott — Tue, 19 Oct 2010 16:46:04 +0000

Another great application for this is for testing string manipulation code, but not preserving the changes.

Say you want to create some code to remove carriage returns from cells in hundreds of different workbooks, testing the batch code will throw up a “Save changes?” dialog each time you try to close the workbook and access another. By suppressing the warnings (and assuming you are using some sort of internal cataloging method to test that your code is doing it’s job, debug.print being a simple way to do so) you can quickly test the batch-readiness of your code.

Thanks for the tips!

By: John D

John D — Tue, 17 Aug 2010 15:34:40 +0000

This code really helped me for a small project I’m doing, thanks a bunch!

By: Keith Bricknell

Keith Bricknell — Wed, 24 Jun 2009 14:10:18 +0000

Set up a scheduled task to open excel, query an sql database, create a new (non-query) workbook with the results. Attached the new workbook to an email and sent it.

works a treat, the only bit I was missing was displayalerts = false!

thanks!!!!

By: Monit

Monit — Fri, 15 May 2009 05:56:11 +0000

Worked for me… thanks

By: Brendan

Brendan — Thu, 04 Dec 2008 01:41:44 +0000

@ross, mark.

Might not be particularly useful in general Excel use, but has a fantastic use in programming Excel from other applications using COM automation.

appExcel.DisplayAlerts = False
appExcel.Quit

Inside the exception procedure if something else gets ballsed up. This prevents having a hundred EXCEL.EXE processes in the background while you’re debugging, because every “New Excel.Application” spawns a new Excel process.