adobe activeX control in VBA application

[Guest]

Hello,

I am trying to use Adobe reader ActiveX control in MS-Access 2010 VBA application (32 bit), but I get 'OLE server isn't registered'.

How can I register the OLE server?

Things I tried:

- reinstall Office 2010 Professional

- reinstall Adobe Reader DC

- manually set reference for adobe reader

I keep getting this error message.

What do I need to do to get the reader to work.

Best regards,

Emphyrio

[Test Screen Name]

Which activex control? what do you want it to do?

[Guest]

Hi,

I just want to view pdf's on a form by having a pdf viewer control. I select ActiveX controls on a blank form in design mode and select the PDF viewer. I then see a square control on the form with the pdf logo in it. If I look at the properties of this control I see:

OLE class: Adobe Acrobat DC Browser Control Implementation

Class: AcroPDF.PDF.1

In the VBA references I see that a reference to this library has been made: Adobe Acrobat Browser Control Type Library 1.0

If I open the form I get the message: "The OLE server isn't registered. To register the OLE server, reinstall it."

If I click OK, I get the message: There is no object in this control".

If I click OK again, I see the form with a blank square where the pdf viewer control is.

I also tried to use the "Adobe Acrobat DC Browser Control Implementation", but this ActiveX control gives the OLE server error already before it puts the control on the form,..

I already tried reinstalling Adobe Viewer. Currently installed version of Adobe Reader is 15.023.20056, the latest download I made a few days ago...  Do you know how to solve the issue?

BR, emphyrio

[Guest · Accepted solution]

Hi there,

I managed to resolve the issue myself. I uninstalled Adobe Reader DC and installed Adobe Reader XI. The Adobe Viewer control immediately works. So the problem is with the DC implementation of the reader. Perhaps something to look into by the SDK team. For now I will work with the XI version.

Thanks, Emphyrio.

[AdobeNewbieDan]

I know this thread is a year old, but any idea if this was resolved? I have to start working on an Access application tomorrow and obviously would like to avoid foreseeable problems.