We have a 32-bit application using PDF Converter v4.5.1.0 to convert Word/RTF files to PDF and it works fine on 32-bit systems.
But terminal server users on a Windows Server 2008 64-bit SP2 machine get the 'Output File Name' dialog when our application tries to print despite using the NoPrompt option. If they click continue, the pdf is created but we don't want the dialog displayed plus it messes up the filename by prefixing 'Microsoft Word VIewer' onto the filename and truncating the unique ID number we assigned it. This happens even for a user logged in as an administrator but not for non-terminal server users.
We are using the Lock function in conjunction with setting Windows Explorer to show file extensions. This is because another customer using Windows 2008 64-bit (but R2 this time) had terminal server users occasionally getting documents printed by other users and this fix ensures users get their own documents. But it doesn't work for the other customer.
Is there anything else I can try? Could it be compatibility with other applications like Adobe Reader?
