Is this a Useful PAX tip?
Posted: Fri Aug 05, 2022 3:48 pm
L & G
A user was moaning that, when he was moving from Cell to cell in a spreadsheet with PAX enabled, it was taking 5 seconds.
So PAX was intercepting an event and doing 5 seconds of work and then returning control to Excel to move the cursor.
We told him to type and run this in VBA: "Application.EnableEvents = false" and the problem went away. Furthermore all explicit actions such as PAX refresh, the Panel etc all worked fine.
So is this a handy way to resolve this problem, or a fool's paradise. We haven't exhaustively tested this, and told the user to try it and see, as it was making his work impossible otherwise.
But what if killing events for PAX may introduce further subtle errors? Does it use events to build internal structures which might become out of sync with reality?
Does anyone know what events PAX intercepts and what it does before returning control to Excel?
What could it possibly do in the 5 seconds of delay our user was experiencing? (The user speculated it was to do with External References as they had recently moved to a slower more secure server and were seeing slowness across the board. But why would PAX care about these?)
If anyone can shed a light on this it would be much appreciated. I'll let you know how our user gets on too...
A user was moaning that, when he was moving from Cell to cell in a spreadsheet with PAX enabled, it was taking 5 seconds.
So PAX was intercepting an event and doing 5 seconds of work and then returning control to Excel to move the cursor.
We told him to type and run this in VBA: "Application.EnableEvents = false" and the problem went away. Furthermore all explicit actions such as PAX refresh, the Panel etc all worked fine.
So is this a handy way to resolve this problem, or a fool's paradise. We haven't exhaustively tested this, and told the user to try it and see, as it was making his work impossible otherwise.
But what if killing events for PAX may introduce further subtle errors? Does it use events to build internal structures which might become out of sync with reality?
Does anyone know what events PAX intercepts and what it does before returning control to Excel?
What could it possibly do in the 5 seconds of delay our user was experiencing? (The user speculated it was to do with External References as they had recently moved to a slower more secure server and were seeing slowness across the board. But why would PAX care about these?)
If anyone can shed a light on this it would be much appreciated. I'll let you know how our user gets on too...