For what it's worth, I haven't noticed this behavior in Excel. I have Office Pro Plus 2019 and I do a lot of automation in Excel, a little in Outlook and Access, almost none in Word.
Thinking about a possible explanation, it occurs to me that you may have an event turned on that executes VBA code when you open a workbook....here it is, WorkbookOpen. If that's waiting to execute, then it'll execute when your code opens a workbook, and what happens after that depends on what your WorkbookOpen code does. If this is the case, you can prevent it by turning Application.EnableEvents off before opening the workbook, and restoring it afterward.
One other possibility (and here I'm stretching): Maybe the workbook you're opening has active content itself, and somehow it's getting control?
|