Search results

1) In the next monthly build, so end of this month/early next month 2) We are unable to repro this, can you share a database and specific repro steps?

This is a known issue and will be fixed soon

Due to an oversight on our end it wasn't included in the runtime in the last monthly build, but it should be included in the build that releases in the next few days.

Some code external to Access changed and resulted in RetrieveJavascriptValue breaking. I locally reverted their change, and that javascript works fine. I'll talk to the team to pull that change before it hits prod. Thanks for reporting, very helpful :)

What javascript are you using in retrievejavascriptvalue? And thats strange that the control works in headers/footers for reports but not forms, as under the hood they're essentially the same thing. I can look into that

Is there any reason why you can't just set a control source with a space in it? Seems to work for me. I would post a link as example but the forum thinks I'm spamming :( I'll still fix this though as the hyperlink dialog automatically encodes urls even when they local, and I have a fix ready...

Huh, we definitely did not intend to block this for any reason, I'll investigate

It is very unlikely that we will get local office files working

Good news and bad news. Good news is if you set the browser control to the address it redirects to, it works fine. Bad news is with the links you posted, the redirect isn't an inherent feature of WebView2, the underlying engine both Edge and Access are using, but rather a feature of Edge itself...

For opening office docs, are you able to achieve this in the regular Edge App? If you can I will look into it, if not, then this doesn't sound like something that would be possible.

You can continue to give feedback even after GA, but anything you think is super urgent should be brought to our attention in the next couple weeks.

Yeah sorry about that, the change to options were not properly hidden, but we expect to release to prod late April, or early May, whenever the new Office monthly fork rolls out

Thanks for the kind words. Yes, we definitely plan to support local pdfs and images, its a known issue that we're working to resolve.

Also, the Object property no longer exists, its an error that it was included in the documentation. The Object property directly links to the old browser OLE object with the nice VBA API, but the new browser is not OLE, nor does it have a built in VBA API

Try RetrieveJavascriptValue "document.getElementById('latbox').value"