A

Anonymous

Question

The AcroPDF.PDF Class is no longer accessible from VisualBasic6 after update 11.0.0.7.

Forum|Forum|11 years ago
May 14, 2014
15 replies
61765 views

After upgrading to 11.0.0.7 of Acrobat Reader it is no longer possible to get an instance of the AcroPDF.PDF Control in Visual Basic 6

Private PDFExt As VBControlExtender

Set PDFExt = Me.Controls.Add("AcroPDF.PDF", "PDF")

This worked fine with the 11.0.0.6 Version of the Reader!

Is there any solution available?

Thanks in advance

Stefan

Acrobat SDK and JavaScript

This topic has been closed for replies.

N

Nikimitsy

Participant

I am a newbie, using excel 2013 and have created a few basic programs to read pdf files from our network within a userform, now i am unable as to form will not even load without error. So i understand the new release is a 64bit application, so my question is how do i load the adobe pdf control into my userform

thanks in advance

A

Anonymous

Hi all,

Any solution from Adobe?? I see..... all developers and programmers used their own solution, but nothing from adobe itself?

Adobe had the best file format ever existed, then they turned it to a bunch of rubbish... the PDF reader was 12kb in early times.. now?? I even dont know... full filled with rubbish which less than 5% of daily users find useful.

I've been thinking to shout it out.. but always leaving my comments to later... but now?!!! After "legacy" Applications which used PDF for years, almost 2 decades, just stop working and there is no solution from adobe? seriously??

I'm commissioned to test environment for a company with about 20.000 users upgrading to windows 10.. using theirs very old VB6 application (which is running just FINE) but the solution of using a webbrowser object to open/read PDFs did not work with windows 10 and the latest PDF reader!!!

My solution to them??? EASY.. CONVERT ALL 1.000.000 DOCUMENTS FROM PDF TO XPS Documents.. XPS is now the easiest format to create.. its HYPER-FAST reader is "native and free" within the windows xx also we can open/read it via web browsers AND AND AND not full of "greebles"!!!

It will take 1 week to convert all docs, and no programmatic needed.. cost effective and no more headache in the future.

So, dear Adobe... bye bye.. for one of largest companies in that country. They will never hear about PDF again.

I will revisit this thread in a week or two to see if adobe takes any actions.. but I dont believe they will...

For all of you developers/programmers out there, I wish the best of luck!

Regards,

MBS the Ex-PDF user

A

Anonymous

VB6 Solution: Add a "Microsoft WebBrowser control" (ieframe.dll) to a form and use its Navigate method to open the PDF file.

Examples:

WebBrowser1.Navigate txtFile.Text

WebBrowser1.Navigate Filename

lrosenth

Adobe Employee

This has been discussed before - VB6 hasn't been supported for a LONG time...

A

Anonymous

Anyone have any solution for VB6.

H

hbarclay

Participating Frequently

The message you sent requires that you verify that you

are a real live human being and not a spam source.

To complete this verification, simply reply to this message and leave

the subject line intact or click the link below:

http://www.barclaysoftware.com/cgi-sys/bxd.cgi?a=harry@barclaysoftware.com&id=nAZTPcGqqYUpXUnoFhWmA-1401373238

The headers of the message sent from your address are shown below:

From forums_noreply@adobe.com Thu May 29 09:20:38 2014

Received: from mail0.phx1.jivehosted.com (:42678 helo=mx1-out1.phx1.jivehosted.com)

by volkswagen.websitewelcome.com with esmtps (TLSv1:DHE-RSA-AES256-SHA:256)

(Exim 4.82)

(envelope-from <forums_noreply@adobe.com>)

id 1Wq1CA-0006sj-JT

for harry@barclaysoftware.com; Thu, 29 May 2014 09:20:38 -0500

Received: from adobe-v7-wa05.m2phx1.jivehosted.com (lbs1.phx1.jivehosted.com )

by mx1-out1.phx1.jivehosted.com (Postfix) with ESMTP id 6DCB3602A5F

for <harry@barclaysoftware.com>; Thu, 29 May 2014 14:20:36 +0000 (GMT)

A

Anonymous

Estimado

Reciba un saludo desde Ciudad Victoria, Tamaulipas, México.

Atentamente

Dr. Ignacio M Morales Flores

Cirujano general y Programador de Aplicaciones Prácticas

http://cpimario.com

http://consultapractica.com

A

Anonymous

FYI

PDF applications built with VB6 fail to work with 11.0.07

A

Anonymous

Thanks Singulus1 ... that solution worked perfectly for us, just have to go through the release process to get it out there now

A

Anonymous

solution for Delphi users.

copy oleCtrls.pas to oleCtrlsAdobe.pas.

then remove from TOleControl:

- IServiceProvider
- function QueryService(...): HResult; stdcall;
- function TOleControl.QueryService(..): HResult;

the definition looks as follows:

TOleControl = class (Twin Control, IUnknown, IOleClientSite,
IOleControlSite, IOleInPlaceSite, IOleInPlaceFrame, IDispatch,
IPropertyNotifySink, ISimpleFrameSite)

then replace in the unit AcroPDFLib_TLB.pas OleCtrls by OleCtrlsAdobe.

A

Anonymous

Worked perfectly! Please reply too in Re: update 11.0.07 causes ActiveX crash on Delphi applications

Thanks for the great help!!!!

A

Anonymous

We too have had issues since upgrading our desktops to 11.0.0.7, I have had to uninstall it and re-install 11.0.0.6 on all of our desktops to enable our programs to work.

As this worked before this update surely it is an Adobe issue.

A

Anonymous

Currently on the market are still 32-bit operating system (32-bit Win8 for example).
It 's absurd that AcroPDF no longer supports 32-bit applications.

Best Regards

Carlo

A

Anonymous

Totally agree with what you say.

Please can someone from Adobe please confirm whether or not a fix will be available especially for those of us who still develop only 32 bit applications (we're still on Delphi 2007). It has been a week now since the release and I would expect a little more clarity from you.

I find it quite bizarre that such a major impact change was made in such a minor release from 11.0.06 to 11.0.07!!

So far, I find Adobe's attitude on this somewhat cavalier.

A

Anonymous

Possible temporary SOLUTION (only for view pdf) for DELPHI users (waiting for a fix from Adobe).

step 1) remove TAcroPDF from your form.

step 2) put TWebBrowser component in your form.

step 3) replace the line of code "AcroPDF.src:=Filename" with the line TWebBrowser1.Navigate('file:///'+Filename)".

It work fine (tested with Delphi2007 in both Win32/Win64 environment with a variety of default browser).

A

Anonymous

I am a developer of an Italian software house.

Our product is developed in Delphi.

The display of *. Pdf via TAcroPDF no longer works for many of our customers and we are in serious trouble.

Best Regards

Carlo

lrosenth

Adobe Employee

OK - here is the situation.

With Reader 11.0.7, we (finally!) now provide a 64bit version of AcroPDF.dll so that Reader can be used in 64bit browsers! Great news for customers.

However, that means that anyone who built an application with an older development environment (eg. VB6) that doesn't know from 64bit DLLs (or "universal" 32/64bit DLLs) will no longer be able to load AcroPDF. As these older environments have not been supported by Adobe for many years now (I think we dropped support for VB6 around Acrobat 9), we didn't test this scenario.

For those of you who are using modern development environment but had previous built your apps as 32 bit (because of AcroPDF) - you can now simply rebuild as either 64 only or "Any" and not only will things work again but you're app will now be 64bit!

Hope that helps everyone understand the situation and how to remedy it.

If you have any questions, please don't hesitate to ask.

M

MonaLisaML

Participant

I don't understand Adobe why its not possible to build a 32bit version as a package only rename file if need be like AcroPDF32.dll then make no further changes to it and have a separate package for 64bit.

This way you are able to have both the 32bit and 64bit versions of your product installed and everyone would be happy. This method wouldn't be reliant on Microsoft OS deciding correct dll version to load as there would be only one choice for the package ... we know this works because users have been okay from v9 up to v11.0.6 where you claim not to support VB6 anymore ???

I agree with you there.

We are using the pdfviewer-control since Acrobat 5 and have now 3 different classnames in our program ("AcroPDF.PDF", "PDF.PdfCtrl.6", "PDF.PdfCtrl.5"), that we try one after the other. It would really be the easiest thing just to add another one e.g. AcroPDF32.PDF.

That shouldn't be a too big a problem for Adobe and would probaly help a lot of otherwise very unhappy programmers ;-)

By the way: The Adobe statement about VBA seemed a bit like a bad joke to me...

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded