PDFs no longer open in the legacy IE browser control (4 Viewers)

[isladogs]

@KitaYama
I'll contact the Access team again later today to check if there is any progress on the issue with PDFs in the legacy browser control.

Before I do so, can you elaborate on the issues with logging into a website with a user name & password in the Edge browser control.
Its not something I've ever needed to do so I don't have an example to test with
Do you have something you could upload for me to use for testing (using either browser control).

 

[GPGeorge]

@KitaYama

I'll contact the Access team again later today to check if there is any progress on the issue with PDFs in the legacy browser control.

Before I do so, can you elaborate on the issues with logging into a website with a user name & password in the Edge browser control.
Its not something I've ever needed to do so I don't have an example to test with
Do you have something you could upload for me to use for testing (using either browser control).

While I can't share the accdb, I can confirm that with the legacy browser control I used to be able to log in to a site. I asked Claude AI for a version that would use JS to log in with the Edge browser control, but I failed to get it to work. Fortunately, it's not that big of a deal in this instance and now I just let the Browser control load and then log in manually a couple of times a week when I need to. The browser does remember by my credentials to make it easier.

The point is, it's a whole different ballgame code-wise and more than a little PITA and I would be displeased if I had to support clients' usage.

 

[KitaYama]

This is a very simplified version of something you can work with in legacy web browser.
The form has a web browser control that opens a web site. The target page has two textboxes and a button to click for login.
Form's on-load event calls Kedi_LogUserIn. The textboxes are filled and the button is clicked. User doesn't need to do anything. This works in legacy browser. After more than a week, neither Copilot nor Chatgpt could offer a code that can do the same in modern web browser.

Option Compare Database
Option Explicit

Private Browser As Object

Public Function SetBrowser(frm As Access.Form)
    Set Browser = frm.wBrowser.Object
End Function

Public Sub Kedi_LogUserIn(frm As Access.Form)
    If Browser Is Nothing Then
        SetBrowser frm
    End If
 
    With Browser
        Do While .Busy Or .ReadyState <> 4
            DoEvents
        Loop
        .Document.all.Item("USER_ID").Value = "********"
        .Document.all.Item("PASS_WD").Value = "**********"
        .Document.all.Item("Login_Button").Click
    End With

End Sub

Public Sub CloseBrowser()
    Set Browser = Nothing
End Sub

Form's event:

Private Sub Form_Load()
    Kedi_LogUserIn Me
End Sub

Private Sub Form_Close()
     CloseBrowser
End Sub

 

[isladogs]

Many thanks. Looks straightforward enough.
I’ll test it using the legacy browser control and assuming that works, I’ll then try adapting it for the Edge browser control

If anyone else has got similar code to work using the Edge browser control then I’d like to hear about it … and I’m sure @KitaYama would like to know as well.

 

[xavier.batlle]

This is a very simplified version of something you can work with in legacy web browser.
The form has a web browser control that opens a web site. The target page has two textboxes and a button to click for login.
Form's on-load event calls Kedi_LogUserIn. The textboxes are filled and the button is clicked. User doesn't need to do anything. This works in legacy browser. After more than a week, neither Copilot nor Chatgpt could offer a code that can do the same in modern web browser.

Option Compare Database
Option Explicit

Private Browser As Object

Public Function SetBrowser(frm As Access.Form)
    Set Browser = frm.wBrowser.Object
End Function

Public Sub Kedi_LogUserIn(frm As Access.Form)
    If Browser Is Nothing Then
        SetBrowser frm
    End If
 
    With Browser
        Do While .Busy Or .ReadyState <> 4
            DoEvents
        Loop
        .Document.all.Item("USER_ID").Value = "********"
        .Document.all.Item("PASS_WD").Value = "**********"
        .Document.all.Item("Login_Button").Click
    End With

End Sub

Public Sub CloseBrowser()
    Set Browser = Nothing
End Sub

Form's event:

Private Sub Form_Load()
    Kedi_LogUserIn Me
End Sub

Private Sub Form_Close()
     CloseBrowser
End Sub

Yo have to use JavaScript to "talk" to new Edge Browser.
Try something like this as starting point:

Option Compare Database
Option Explicit
' Using generic Control to avoid "Type Not Defined" errors
Private BrowserControl As Access.Control

Public Sub Kedi_LogUserIn(frm As Access.Form)
    If BrowserControl Is Nothing Then
        SetBrowser frm
    End If
 
    Dim jsCode As String
 
    ' JavaScript is the only way to talk to the New Browser

    jsCode = "document.getElementById('USER_ID').value = '********';" & _
             "document.getElementById('PASS_WD').value = '**********';" & _
             "document.getElementById('Login_Button').click();"

    ' Using .Object to access the Edge-specific ExecuteJavascript method
    On Error Resume Next
    BrowserControl.ExecuteJavascript jsCode
 
    If Err.Number <> 0 Then
        MsgBox "Could not execute login script. Ensure the page is fully loaded.", vbInformation
    End If
    On Error GoTo 0
End Sub

 

[isladogs]

@xavier.batlle
Answering from an Edge browser control in Access!
Yes, you need to use Javascript for the Edge browser control but also need to avoid using .Object as that isn't available in the Edge control

 

[isladogs]

Experimenting with logging into this site using an Edge browser control
The code enters my user name & password correctly but the login button doesn't get clicked

Not sure if that's because there are 2 alternative buttons that can be clicked to login or if the site is blocking automated logins

 

[Albert D. Kallal]

@KitaYama
Thanks for confirming that the legacy browser control no longer displays PDFs even in versions as far back as 2508 (which used to be OK). To me that acts as further confirmation that the problem is due to a January Windows 11 update and not Access itself, as I first suggested back in post #1.
I also don't believe Acrobat is the problem as users who don't have that installed have the same issue.

@Albert D. Kallal
The issue is nothing to do with the Edge browser control in Access nor with the Edge browser itself
It is specifically that the old Access legacy browser control no longer displays PDFs for users running recent versions of Win 11. Win 10 is OK

Ah, very well. Of course the legacy IE access browser control actually does not have PDF ability built in. It relies on AcroPDF.dll, and that's been removed from newer installs of windows 11........

So, if you install a older version of Adobe reader, then Access IE should then start to render PDF's.
So, since we ARE using the older browser here, then windows 11 in theory should/will require AcroPDF.dll, and that means installing a legacy version of Adobe to make this work.

Hence, you could try installing a older version of Adobe reader:

link removed - wrong one....

So, a fresh win 10, or a fresh win 11 NEVER could display a pdf inside the Access browser control. This only worked AFTER having installed a pdf viewer.....(which most people did). Now that browsers can display PDF's, then "more often" a win 10 or win 11 pc will not have a pdf viewer having been installed. Your first screen shot shows pdf "icon", but it's the one from the browser -- but NOT the legacy one from Adobe!

It's certainly possible that windows updates removed, or broke the AcroPDF.dll, or un-registered it.

Either way, then when trying to display a pdf, we see the attempt to use the newer browser if a working .pdf viewer (non browser based one) does not exist or is not available (and thus the default extension for pdf's points to the newer Edge Browser). So, in a round about way, your first screen shot shows that Edge browser trying to open the .pdf, since the .pdf extension is now associated with the Edge browser (so, yes, the Edge browser is involved in this issue).

So, either re-registering AcroPDF.dll, or installing a older Adobe PDF viewer should fix this issue......

However, perhaps re-associating the .pdf extension with the Adobe Reader as opposed to the Edge browser as your screen cap shows would also fix this issue...... (so, Edge is relevant here, since it sure looks like Edge has stolen the .pdf extension as per your first screen shot.....).


R
Albert

 

[isladogs]

Hmm...
I agree with some of that but I don't believe its entirely true. Rather than speculate, I've tested most of your comments above.

Back in the day, it was certainly true that PDF wouldn't open within Access unless Acrobat Reader had been installed.
I've just confirmed that on an old A2010 / Win 10 VM and got the same Open / Save dialog without Reader installed..

However, I'm fairly sure that AcroPDF.dll hasn't been a requirement for many years with Edge and other browsers having PDF functionality.

My screenshot in post #1 was from a Win 11 laptop that had never had Acrobat Reader installed and has Edge as the default app for opening PDFs as stated. I've not rolled back Win 11 to before the Jan updates because I know that I could previously open PDFs in the legacy browser control (as well as the Edge browser control).

As many others have reported both here and on other forums, the legacy browser can no longer open PDFs in Win 11 (but is still OK in Win 10)
This change occurred after one of the Win 11 Jan 2026 updates.

As a test, I just installed first a 2022 version of Acrobat Reader then the latest version.
The legacy browser control no longer shows the Open or Save dialog from post #1 but it does show the blank grey box as others have reported - still no PDFs shown

And I tried making Acrobat the default - no effect whatsoever.

 

[xavier.batlle]

@xavier.batlle
Answering from an Edge browser control in Access!
Yes, you need to use Javascript for the Edge browser control but also need to avoid using .Object as that isn't available in the Edge control

I don't use the Edge WebBrowser control, but I tested it when I watched this interesting video by Richard Rost:

 

[isladogs]

I've tried multiple different variations of the Edge browser control. None actually click the Login button.
It may well be that this site is blocking automated login clicks
@Jon would be the one who could definitively answer that

For now I'm putting this to one side. Perhaps, tomorrow I'll try some other sites
Bearing in mind neither @KitaYama nor @GPGeorge were successful, it seems there is a more widespread problem

 

[KitaYama]

I've never been able to share a database here. Here's the reason.
But I give it another try.
If you can open the form in the shared database bellow and are not receiving errors, you will see the following page. It shows that you were able to input a username and a password and clicked the button of a login page, but your credential is not correct and login failed.
If you input the correct username/password, login will be successful and you'll see customer page.

Unfortunately I can not share the correct username and pass and I'm sure you understand why.
As a further test, if you delete the following line, you'll see the textboxes are filled.
.Document.all.Item("Login_Button").Click

If you receive errors on the form, you may need to export the form as text, edit the names and any strange character and import it again.
If you still don't have luck with it, you may want to reconstruct the form in a new database. If so, add the web browser control by using the following button and change the name to www and import the vba code for events and the module.

This doesn't work if I change the browser to New Browser control. I've been trying to solve the problem with different AIs for days but nothing happens. Any possible solution, javascript included has been tested and returned negative.

 

[Albert D. Kallal]

Hmm...

However, I'm fairly sure that AcroPDF.dll hasn't been a requirement for many years with Edge and other browsers having PDF functionality.
.

Above is correct, but still in ALL cases, the browser control in Access ALWAYS did require the Adobe plug in....


Did you try installing the older legacy Adobe reader?

And I tried making Acrobat the default - no effect whatsoever.

Has to be a older legacy version that includes AcroPDF......

I'm just going for coffee, and I have that win 11 vm. It has no pdf viewer, will try Access (have to use runtime) and see if the pdf shsows.
(I doubt it will).

From what I recall:
The original Edge (EdgeHTML engine), from some point to 2020 did have a built-in pdf viewer, but Access could NOT use it!!
(hence adobe AcroPDF.dll was required).

And that older edge never exposed a plug-in that Access could use....

And from what I recall, then Access could ONLY ever use the AcroPDF.dll. Edge chrome engine browser did not change nor fix this issue.

When Adobe removed that plug in, then Access could not render PDF's.....

So, even with legacy Edge, even when it did get/or have PDF ability? Access could NEVER use it....
And even with the new Edge, again, did not matter....

But, Adobe Reader DC still shipped the AcroPDF.dll.... (now it does not....)

Around win 10, then Edge Chromium appeared - and it again can display PDF's, but again, Access did not use that feature - it will still showing PDF's via the Adobe path/plug in.

The problem thus is Adobe does not include the AcroPDF.dll anymore -- and this occurred during the win 10 to 11 transition.

Hence, installing a legacy Adobe reader should fix this issue, using the newer version Adobe will NOT work
(so, any version of Adobe such as 2021.007.200099 or earlier should work).

so, say this one:

https://ardownload2.adobe.com/pub/adobe/reader/win/AcrobatDC/2200320310/AcroRdrDC2200320310_en_US.exe

I'll test this in a bit when I can remote into that vm of mine....

Confirmed!!!!!!!!

So, as I suspected:

Access web control NEVER at ANY point in time could show a PDF unless the AcroPDF.dll was installed correctly.
Access at no point in time could display a PDF, and the newer or older edge did not matter.

In above test, fresh win 11 vm, Access could not display the PDF, the behavour was exact as yours - you get a external prompt to open the PDF (makes sense at least to give that option, since Access can't display the pdf). This then would launch the web browser, since at this point in time I did NOT have Adobe reader intsalled.

Installing the legacy version of Adobe, it now works...... (and first time I did it, I got a prompt from Adobe -- EULA....).

Bottom line:
You need the AcroPDF.dll, and if I have time, I'll test to see if that one .dll can be just registered without installing the reader - but regardless, we have a working solution......


R
Albert

 

[isladogs]

@KitaYama
Very strange. What you provided is exactly what I made after your PM earlier
However this time it worked exactly as expected. No idea why it didn't for me earlier

Not only that but with almost no changes to the code, it also works for that web login page with the Edge browser control (attached)
Can you check with the correct userID / password combination. Thanks

===================================================
EDIT:
This thread is now getting very muddled with two unrelated conversations going on and would be better split.
Tomorrow I'll ask one of the mods to move all the posts about login forms starting with post #20 to a different thread.
I think that's posts 20, 22 to 27, 30 to 32 and 34 (this one).

 

[isladogs]

Did you try installing the older legacy Adobe reader?
Has to be a older legacy version that includes AcroPDF......

Yes - I said I tried both older (2022) using your link & then the latest versions in turn.
You quoted my comments.

As a test, I just installed first a 2022 version of Acrobat Reader then the latest version.
The legacy browser control no longer shows the Open or Save dialog from post #1 but it does show the blank grey box as others have reported - still no PDFs shown

Neither worked

 

[Albert D. Kallal]

bump my post - see edit that first link was WRONG WRONG -- my bad.......
Must be 2021.x, or older -- 2022 Adobe will not work.....

 

[KitaYama]

This thread is now getting very muddled with two unrelated conversations going on and would be better split.

It's all my fault. I simply was trying to explain why our forms have two browsers controls one above the other. One for logins, the other for pdfs.
I stop here and will stick to pdf problem. I will test your file and will answer in a PM.
Thanks for your time.

 

[Albert D. Kallal]

Neither worked

So, in summary:
Access web control NEVER could display a pdf - regardless of browser installed.
Access web control STILL requires the AcroPDF.dll, and you thus MUST install a version of Reader DC 2021.x, or previous.......

My sincere apologies for having provided the WRONG Adobe link to try.......

Try the current link, this one, it does work for me:

https://ardownload2.adobe.com/pub/adobe/reader/win/AcrobatDC/2200320310/AcroRdrDC2200320310_en_US.exe

R
Albert

 

[KitaYama]

So, in summary:
Access web control NEVER could display a pdf - regardless of browser installed.
Access web control STILL requires the AcroPDF.dll, and you thus MUST install a version of Reader DC 2021.x, or previous.......

My sincere apologies for having provided the WRONG Adobe link to try.......

Try the current link, this one, it does work for me:

https://ardownload2.adobe.com/pub/adobe/reader/win/AcrobatDC/2200320310/AcroRdrDC2200320310_en_US.exe

R
Albert

I need a confirmation before testing.
What will happen if someone has Adobe Acrobat pro installed? Does using this legacy reader interferes of break anything?
Thanks