It's indeed the rendering process however, it seems that it works correctly when not setting the horizontal anchor point of the control to both sides. If i do set it, then it shows the white space. We could use this work around but if it's possible, we would rather use the anchor point because then we won't need to look at the width.
![[Image: change-to-Horizontal-Anchor-300x300.png]](https://www.iaccessworld.com/wp-content/uploads/2016/09/change-to-Horizontal-Anchor-300x300.png)
(The anchor point of the control, this is just an example of what i mean)
To give you some additional information:
There is no problem when using the Edge browser.
The screen resolution is 1920x1080
The DPI is set to 100%
I'm using Access 365, 16.0.1, 32Bits, on a Windows 10 machine. (Access 2010 has the same problem)
The form height is 6,508cm and width 8,492cm. However, since im achoring it, it'll become full screen.
(The anchor point of the control, this is just an example of what i mean)
To give you some additional information:
There is no problem when using the Edge browser.
The screen resolution is 1920x1080
The DPI is set to 100%
I'm using Access 365, 16.0.1, 32Bits, on a Windows 10 machine. (Access 2010 has the same problem)
The form height is 6,508cm and width 8,492cm. However, since im achoring it, it'll become full screen.