Imagine an add-in that allows the user to create custom maps based on data in an Excel workbook. When AutoSave is enabled, this code runs automatically on a periodic basis, which has the potential to interrupt the user, especially if the code takes a long time. When AutoSave is disabled, this code is only run when the user explicitly chooses to save, so a delay is not as noticeable and can be avoided by the user until he or she is ready to save. Therefore, if your code in a BeforeSave or AfterSave event handler takes too long to run, it may significantly degrade the user experience. In general, Word, Excel and PowerPoint are not responsive to user interaction while add-in or macro code is being run. Issue 1: Code in BeforeSave or AfterSave events runs too long
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |