Thanks guys for your comments. What's particularly strange is that this only occurs for 2 Reports in the DE - compiled code works fine.

>Last year I looked at it and ran into a wall (for my usages at least);
>They had stripped all DOM manipulation via the Document Object.
>Back then the only "WebBrowser" interface (ShDocVw.dll >> ShellDocView AFAIR) seemed targeted
>
>No way to get to the MsHTML Interfaces to manipulate the DOM directly:
>Which was my main mission years ago: Scanning and Tweaking the Document.
>Rick manipulates Chromium WebView2 directly and sometimes posts problems encountered there.
>My basic idea would be to call over a JS bridge, but that is just one of the pain points Rick mentions.
>
>So yes, look at it if you need it, but be careful with promises based on prev experience.
>And PLEASE post about ways to make Chromium behave internally / tweak the DOM ;-)
>
>Interested but sceptical
>thomas
>
>>See that Microsoft has released what they call the New Modern Web Browser Control which uses Edge in Access. Has anyone gotten this to work with VFP?
>>
>>https://www.google.com/search?q=access+new+modern+web+browser+form+control&oq=New+Modern+Web+Browser+&gs_lcrp=EgZjaHJvbWUqCAgBEAAYFhgeMgYIABBFGDkyCAgBEAAYFhgeMgoIAhAAGIYDGIoFMgoIAxAAGIYDGIoFMgoIBBAAGIYDGIoFMgYIBRBFGD0yBggGEEUYQTIGCAcQRRg90gEJMTYxNDNqMWo3qAIAsAIA&sourceid=chrome&ie=UTF-8