MicrosoftMicrosoftColin,
The trouble is V2311 is still the current release (current channel). So even if it is fixed on the insider programme, my clients will have to wait.
For now, I have had to disable the browsing function and remove the bad control from the application. The first time I saw it, it could have been due to Windows 11/10. Then a second client's app died and I suspected V2311. Then my own development PC updated to V2311 and it also died.
It would have been nice to have had the release notes on time to have been able to substantiate my hypotheses that is was a bug in MS365 and not my application. It would also have saved me several hours of debugging. A three week delay is simply not acceptable.
My application is way too complicated to be used as a demo, but I did manage to distil the problem down to the nested event procedure behaviour I describe. Do you need me to provide a demo database exhibiting the problem? It will have to wait for the New Year though.
