I have an issue using the PDF-XChange SDK sample code with Microsoft Visual Basic in 'Interactive Mode' for debugging.
I have an issue using the PDF-XChange SDK sample code with Microsoft Visual Basic in 'interactive mode' for debugging.
Please note that a developer asked this question on the Tracker Software forum. They had copied all example files to the bin directory, but found that when they ran VB6 in interactive mode for debugging an error message appeared:
"Run-time error '53' File not found: xcpro40".
There was no issue when it was compiled to an EXE, but they needed to run in interactive mode for debugging and testing of the product.
This issue arises because the VB 'interative mode' uses DLLs that are located in folders that the PATH environment variable specifies and ignores DLLs located in the projects folder.
Follow the steps below to resolve this issue:
1. Copy all DLLs into any folder listed in %path% - echo %path%.
2. Add the project folder path to the path variable. For example, in Vista it would be:
Control panel -> System -> System Properties -> Advanced -> Environment variables -> System Variables -> Path -> Edit -> followed with a list of absolute folder paths demilited with semi-colons.
Debugging should then work as normal.
More Like This
- KB#227: I have an issue using the PDF-XChange SDK sample code with Microsoft Visual Basic in 'Interactive Mode' for debugging.
- KB#282: Why won't the "Send by E-mail" feature work in conjunction with Microsoft Outlook?
- KB#338: What are the MSI installation switch options for the PDF-XChange family of products?
- KB#447: How do IDetermine what version I should install/how can I retrieve my serial key?
- KB#286: How do Imanage licenses for PDF-XChange Products on a Windows Terminal Server?