Skip to main content
D
dmitry_ccc
Participant
March 16, 2020
Question

Bug in Adobe Reader 2020.006.20034 - DDE connection

  • March 16, 2020
  • 1 reply
  • 1466 views

Adobe Reader keeps DDE service name under the following entry in Windows registry:

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\acrobat\shell\open\ddeexec\application 

 

Adobe Reader 2020.006.20034 has the following value: "AcroViewR19". However DDE connection fails when this name is used. I changed the name to AcroViewR20 and DDE connection was successfully established. So apparently the service name has been changed since previous version, but registry entry has not been updated. 

Please address the issue. We use DDE connection to automatically open proper page of pdf document.

Thanks

 

    This topic has been closed for replies.

    1 reply

    Meenakshi_Negi
    Meenakshi_Negi
    Legend
    March 17, 2020

    Hi Dmitry_ccc,

     

    Thank you for reaching out.

     

    Would you mind sharing more details for further investigation of this issue?

    - Share the OS version on the machine.

    - Let us know the workflow you do when the issue occurs.

     

    We will be waiting for your response.

     

    Regards,

    Meenakshi

     

     

    D
    dmitry_cccAuthor
    Participant
    March 18, 2020

    Hi Meenakshi,

    Thanks for quick reply. Answering your questions:

    - I have Windows 10 Pro, Version 1909

    - Our application establishes DDE connection with Adobe Reader. Below is some simplified code:

    str_dde topic = "Control";

    str_dde service = ReadDDEServiceName(); // reads "AcroViewR19" or "AcroViewR20"from registry

    hDdeConnnection = DdeConnect(hDdeInstance, service, topic, NULL);
    if( !hDdeConnnection ) {  // Note: "AcroViewR20" - succeeds for latest reader, "AcroViewR19" - fails

         clog << "DdeConnect failed."

    }

    // do something

     

    Regards,

    Dmitry

     

    D
    dmitry_cccAuthor
    Participant
    April 21, 2020

    Hi Meenakshi,

    Is there any updates on this bug report? Was this submitted to the backlog? When the plan to address it? I noticed that new version has been released - 2020.006.20042. It has exactly the same issue.

     

    Thanks,

    Dmitry

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices