RolW

I'm another victim. I think the issue first appeared when I migrated from Office 2016 to Office 2024 a few weeks ago. Here's a scenario...