![adobe acrobat distiller xi adobe acrobat distiller xi](https://i0.wp.com/news-cdn.softpedia.com/images/fitted/300x250/Adobe-Flash-Player-Update-Brings-Windows-8-1-Improvements-Free-Download.jpg)
*– This is the "Application" name that the OS sees as doing the printing when running on a 64-bit HKEY_CURRENT_USER. ORegTools.SetKeyValue(lcPrintingApplicationName, “C:\TEMP\JMC_PO_MS2741C.pdf”) LcPrintingApplicationName = _VFP.ServerName *– This RegKey setting works on 32-bit HKEY_CURRENT_USER. M.lcKeyPath = "Software\Adobe\Acrobat Distiller\PrinterJobControl" The main thing is to setup the registry value the right way. Again, this all works the same way whether you are using.
ADOBE ACROBAT DISTILLER XI CODE
(This code uses an instance of the Registry class from the FoxPro FFC classes to work on the Windows registry). Perhaps this is so the next app that prints won’t use the same name.įinally, here’s the VFP code I use to set the values for both 32-bit and 64-bit OS’s.
ADOBE ACROBAT DISTILLER XI PDF
So, with the PrinterJobControl registry key all programmatically setup as described above, when you actually fire off the Adobe PDF printer, the output name is already set and the user will not see the prompt dialog to choose the output path and filename.Īlso, be aware that after *you* programmatically create and set the registry value, the Adobe PDF driver will actually delete that string value from the key right after the file is printed.
![adobe acrobat distiller xi adobe acrobat distiller xi](https://connect-innovation.com/wp-content/uploads/2022/02/adobe-connect-award-2022.png)
Since this spooler thingy exe runs from C:\Windows, the actual registry key that must therefore be created is “C:\Windows\splwow64.exe”. So that’s the application name you have to use, and you do have to include the path. The issue is that the *application* name that the 64-bit OS sees as doing the printing is no longer the actual exe the user is running, but rather some odd Windows exe named “splwow64.exe” (some spooler-like thingy that actually handles the printing which I learned about here ). Well, that’s how it works on good ‘ole 32-bit OS. So, to bring it all together, you add a string value named after the app that is doing the printing (for instance) “C:\Program Files\Microsoft Visual FoxPro 9\vfp9.exe” and you set the value of that string value to the filename you want the PDF to be called i.e. Of course, it’s up to you to decide the path and filename of the PDF output file you’re want to create. Now, the path and filename of the application that is doing the printing is not always easy to figure out, so I can’t solve that mystery here for any given app that you may be using, but I do know (and I forget where I learned this) that for a Visual FoxPro application (.exe), the path and application name can be discovered from the VFP variable “_VFP.ServerName”. So, you create a string value under that key with the path and name of the *application* that is printing the PDf, and then you set the value of that string value to the path and filename of the PDF you want to create. This magic registry key is located at: HKEY_CURRENT_USER\Software\Adobe\Adobe Distiller\PrinterJobControl. I use this technique to automatically set the path and filename for my users for the various PDF reports we generate to send out to our customers and vendors. I’m explaining this from the perspective of a Visual FoxPro application, but the issue applies to all Windows applications, and the remedy can come from many programming languages.īackground… It’s well know that you can prevent the Adobe PDF printer driver from prompting the user to choose a path and filename for the output file by programmatically setting a certain registry key with a string value that contains the desired path and filename of PDF file you want to output.
![adobe acrobat distiller xi adobe acrobat distiller xi](https://i0.wp.com/rahim-soft.com/wp-content/uploads/2018/10/Adobe-Acrobat-Reader-DC-2019-v19-Free-Download-2.jpg)
So, I want to show the remedy in case others encounter this same problem. My MicroTek scanner is not supported, my HP 2800 Business Inkjet is not supported, and I recently discovered that a technique I use in my Visual FoxPro business application to pre-define the PDF output filename when using the Adobe Acrobat PDF printer driver mysteriously does not work on Windows 64-bit.
ADOBE ACROBAT DISTILLER XI WINDOWS 7
Now that I’ve moved over to Windows 7 64-bit on my primary workstation, I’m in a new world of IT support that I didn’t expect from those extra 32 bits of OS horsepower.