![]() ![]() The second workaround that I found is rolling back the O365 update to version 15831.20208 (the last version from 2022). As soon as I try making it a trusted document again, the issues return. If I click enable macros each time I open the workbook but do not make it a trusted document, everything works. I found that if I rename the file, Excel no longer recognizes it as a Trusted Document. ![]() I don't have a fix but have found 2 workarounds so far that at least allow us to keep using the workbook. Oddly, I have several workbooks with macros (one being very similar to my problem workbook) and those all work fine. I know I don't know anything having the same problem after the January update with a workbook that I've used for well over 3 years without issue.Īnd same as you, I found that editing the code would temporarily fix the issue until the workbook was closed and opened again. Hope I was able to help you with this info. These procedures can then be started from anywhere without any problems. The procedures required for OnTime are usually stored in a general module, which is usually the best experience. The OnTime method is used there to update data in the user form at regular intervals. There is also a command - with which you can make a userform run a code over and over again (interval-technical) - as long as the userform is open.Īn example in the included file. If the user form was only hidden using Me.Hide, only the "Activate" event is executed the next time the user form is called - but not the "Initialize" event. This is the case the first time the user form is called (even after a STOP), or if the user form was previously closed with a cross or Unload Me. ![]() but when displaying a UserForm, the event "Initialize" and then "Activate" is executed if it wasn't previously loaded. ![]()
0 Comments
Leave a Reply. |