You can verify this by launching Word the old-fashioned way and opening File1 at the bottom of the File menu after running the sample code.

Although it would be difficult to do an exhaustive test, in theory this should work from any Automation client-Visual Basic, Excel, Power Point, or any other.

Are there other Excel Properties that could be added? Restore CA = Value End Property Public Property Get Restore Display Alerts() As Boolean Restore Display Alerts = this. I actually added the Terminate event in the CR textbox, so I wasn't in IDE/OOP mentality when I added it.

791577-Application-Screen Updating-not-working-in-Excel-2013 https:// test the difference in screen updating, try running the one-and-only macros in these files: first file does not use Application. Adding Do Events, which normally makes Excel responsive while a macro is looping, does not help either situation.

I’m currently on a project to improve the performance of a particular workbook.

Calculation = xl Calculation Manual End With End Sub Public Sub Restore App Settings() With Application . That's potentially a lot of private variables to declare and assign, and it can quickly get confusing about when and where properties are set and unset. You'll want a test for each property you're persisting, that fails when the getter doesn't return the value that was persisted; you'll want a test for each getter again, that fails when it doesn't return the expected value after it was saved and then modified.

Calculation = xl Calc End With End Sub That works well enough when the procedure is viewed in isolation, but it mightn't work very well once the call stack gets deeper. For example, you'll want a test that fails when twice.