Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Unhandled Exception in OCX
Message
 
 
À
20/08/2020 08:08:34
Information générale
Forum:
Visual FoxPro
Catégorie:
Contrôles ActiveX en VFP
Divers
Thread ID:
01675817
Message ID:
01675837
Vues:
84
J'aime (1)
>>>Is it an ActiveX you can get any support with or you're on your own?
>>
>>Thanks for the suggestion, it's the PDF Viewer of Visage (VSPDFViewer.ocx), so probably we could get some support, will check that out. Perhaps we will also look at some alternative controls to see if another would be a better fit. When implementing this control it was very easy to integrate, but we did not test this with all different versions of PDF files.
>
>You should be able to create an embedded Internet Explorer control and open the PDF directly within. See attached. Unzip to c:\temp\ or modify the code and change the click event to wherever you unzip it to.
>

That was the first solution we had right in the beginning, but that is much too laggy. The preview would show the PDF content while scrolling throught the list of documents, and the IE control takes too much time. So while moving in the list you get stuck all the time, while it's trying to load the document. Also we would need to edit the registry to have the control work integrated in the form, and the representation is not always good with Adobe reader, because it shows some menus that are not helpful. So now with the integrated PDF viewer it works really great. Even a PDF file of 40 MB shows up immediately without delay, so it's not a bad control at all.

I wrote to support to see if they can fix it, in the meantime I use PDFtoText to extract the content i case it's produced with the MS Print to PDF function. All other PDF files show without problems.



>>In the meantime I found out that the viewer produces this error only with PDF documents version 1.7 that are created by printing to the Microsoft Print to PDF driver, which produces PDF files that are pretty large. Strangely enough, Word printing to PDF produces also version 1.7, but those are working well.
>>
>>I can work around the problem by investigating the file content and check for "/Producer (Microsoft: Print To PDF)", for those I would the skip the preview just to avoid the message, probably I will also use pdfgrep to at least show the text based content.
Christian Isberner
Software Consultant
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform