M
Michael Purcell
I have an Excel 2000 workbook with a volitle function that is usually
only opened for viewing. To avoid getting prompted to save the
workbook when closing it, I find I can put the following code on the
workbook code page:
Private Sub Workbook_Open()
ThisWorkbook.Saved = True
End Sub
The volatile function evidently is called before the Workbook_Open
event fires, so it is possible to open and close the workbook without
being prompted to save. It seems to me that this is safe, in that if
any changes are made to the workbook after it is opened, the Saved
property will be set back to False, and the user will be prompted to
save. But since I am fairly new to programming VB and Excel, I would
like to know if I am overlooking any negative effects of including
this in a project.
TIA
Michael Purcell
only opened for viewing. To avoid getting prompted to save the
workbook when closing it, I find I can put the following code on the
workbook code page:
Private Sub Workbook_Open()
ThisWorkbook.Saved = True
End Sub
The volatile function evidently is called before the Workbook_Open
event fires, so it is possible to open and close the workbook without
being prompted to save. It seems to me that this is safe, in that if
any changes are made to the workbook after it is opened, the Saved
property will be set back to False, and the user will be prompted to
save. But since I am fairly new to programming VB and Excel, I would
like to know if I am overlooking any negative effects of including
this in a project.
TIA
Michael Purcell