That’s it in a nutshell. I’ve had to recently wipe my Windows 7 64-bit development box and start fresh with the same settings for Windows 8. It’s been a nightmare, but I’m on the home stretch. The references in VB 6.0 points to PDFCreator.Exe but on the new box preceded it with “MISSING:” It is not missing, I have confirmed it is there and have even manually browsed to the file, but it will not register as a reference. Consequently, my applications that use this will not run at all. I do have an older box (XP) that points to the same file, same location, and works fine. Is there perhaps a new reference I need to be including in my applications instead of the one that was previously used? Any help would be appreciated.
I have since eliminated the possibility that it is Windows 8 as the problem, at least not entirely. I installed version 1.6.2 on my XP box and it had the exact same effect, causing the PDFCreator.Exe reference to be flagged as “MISSING” Even the VB 6.0 sample applications will not load and run for the same reason - the invalid reference. Out of frustration I started back-installing to older versions stopping at 1.5.0 but it still does not recognize the reference as being there. My old XP box had something like a 1.0.2 version before I updated it, and I doubt that old version is even available to re-install unless I managed to save a copy somewhere on my system. Obviously not the best of solutions, but I have to wonder why all of a sudden it’s decided to fail on both my new AND my old reliable computers once 1.6.2 was installed.
Hi,
my guess would be it has something to do with 1.6.2 having an updated MSCOMCTL.OCX included. Can you try, if running the PDFCreator as admin once solves the problem?
Otherwise you can find some older versions here: http://download.pdfforge.org/download/pdfcreator/list
regards,
Robin
You are probably correct. I did have to manually uninstall 1.6.2 and then install 1.6.1 and the problem went away. Strangely, allowing the system to automatically uninstall before reinstall did NOT seem to work, at least with other versions. I had immediate access to 1.5.0 and tried that first and there was no change in the problem, but manual uninstall and install of 1.6.1 did the trick. Thanks for your response. Unfortunately, this probably means that I’ll have to stay at this level indefinitely and I’ll have to advise my customers to stay at that version (for now) as well.