We experience issues with the May 30 release of Office 365, from version 2405 17628.20110
We experience issues with Microsoft Access. The issue that we experience is that loading and closing of forms takes longer and longer when you are using the application. Basiccally what we see is that the drawing of the form takes longer each time a form is opened.
We have written a recursive function to illustrate this:
![rkessels_4-1717623631152.png rkessels_4-1717623631152.png](https://techcommunity.microsoft.com/t5/image/serverpage/image-id/589297i207A554F3FAB80A1/image-size/medium?v=v2&px=400)
When we execute the function, this are the results:
![rkessels_0-1717623599931.png rkessels_0-1717623599931.png](https://techcommunity.microsoft.com/t5/image/serverpage/image-id/589293i08E871D7527A66D7/image-size/medium?v=v2&px=400)
…..
![rkessels_1-1717623599935.png rkessels_1-1717623599935.png](https://techcommunity.microsoft.com/t5/image/serverpage/image-id/589295iD74D975C5536E0C8/image-size/medium?v=v2&px=400)
…..
![rkessels_2-1717623599938.png rkessels_2-1717623599938.png](https://techcommunity.microsoft.com/t5/image/serverpage/image-id/589294iEB91F81B9A31DF2C/image-size/medium?v=v2&px=400)
….
![rkessels_3-1717623599942.png rkessels_3-1717623599942.png](https://techcommunity.microsoft.com/t5/image/serverpage/image-id/589296i9A7A3C13CFACF2A1/image-size/medium?v=v2&px=400)
In above overview you can see that when we start the access application the loading of the form takes approx. 0,3s, and the closing of the form takes 0,05s
After 100 opens the timings are 0,5 and 0,3s
After 200 opens the timings are 1,4s and 1s
After almost 300 opens the timings are 2+s and 1,8s
When we execute this same recursive function in an older version of Microsoft access the timings are stable.
We have tested this with several forms. And we see this with all forms. The only difference is the loading speed – which depends on the number of objects that are drawn on the form. The more objects the slower and the higher the increase in becoming slower.
Anyone knows if this bug is already reported / fixed by Microsoft?