OK

Cracked the first part, and should have remembered this!

Using the EnabledEvents = False property in the click button event solves
the doubling up with the Before Close event.

I have also figured out how to set the BeforeClose Cancel argument to True
(Cancel =True) which means BeforeClose is bypassed.

Nevertheless, I now need to know how to stop the Yes/No/Cancel dialog
appearing from BeforeClose when called from another procedure(e.g.
Activeworkbook.Close) rather than giving me the dialog?
(Application.DisplayAlerts = False, doesn't seem to work in this instance?)

Cheers

Joe

"Joe 90" (remove silly spam) wrote in message
...
Hi

Have a workbook that "before close" needs to export several of its sheets to
a new workbook, create a pivot table in that workbook, close and save the
new work book, then get on with closing itself. I have all the code to deal
with this and it works well by itself. However I also run the first workbook
from a set of buttons on the first sheet. One of these is an Exit button,
which saves and closes the workbook. I have also set the Before Close event
in the workbook to do the same thing, so that the user has to save and
close, which ever way they try to close the workbook.

My problem is that introducing the sub procedure in the "before close" event
to deal with the export. For some reason, it doesn't work. What is happening
in the "before close" event that is different from normal?

e.g. my sub needs to unhide 4 worksheets to in order to export them. This
does not happen when run from within the "before close" sub on the workbook.

Hope this all makes sense?

Joe