pdfdriverinit issue
pdfdriverinit issue
I have 2.1 version installed on over 500 computers and has been working for years. Upgraded to 2.5 following instructions on where to deliver files and registering cdintf250.dll in system directory. Thought all was well until I had to set things up on a new machine (no prior pdf stuff installed). I have no desire to use the install.exe. Bottom line is that pdfdriverinit gives a 1797 printer installation failed (printer driver unknown). I'm doing a createobject(cdintfex.cdintfex) which works but as soon as I go pdfdriverinit (giving my own unique printer name) it gives error. (I'm fully aware of admin rights issue and have them). My observation is that if I used the install.exe, then do my pdfdriverinit it works. If I remove the printer created from the install, the pdfdriverinit stops working (or if I install amyuni). i have distributable files in app directory and cdintf250.dll in systems directory registered there. In playing around (and another post) I've noticed that it doesn't seem to find distributable files. If I copy the distrib files in my app directory to the system directory all works. I have no problem delivering the files there but don't won't to break other programs. ?? One of the reasons I moved to 2.5 was because quickbooks was installing something that messed up my program. Any help would be appreciated.
Hello,
The files and dlls of the PDF Converter should be in the same directory as CDIntf250.dll.
So if CDIntf250 is registered in the system directory you need to copy the other dlls to the system directory as well, otherwise, if CDintf250 is registred locally in the same folder as your application you can keep the dlls there.
Hope this helps and Happy New Year!
The files and dlls of the PDF Converter should be in the same directory as CDIntf250.dll.
So if CDIntf250 is registered in the system directory you need to copy the other dlls to the system directory as well, otherwise, if CDintf250 is registred locally in the same folder as your application you can keep the dlls there.
Hope this helps and Happy New Year!