Microsoft Knowledge Base Email Alertz

(167826) - When executing a DDE transaction with Internet Explorer (16-bit or 32- bit), Internet Explorer does not seem to communicate to the application as expected. Internet Explorer's DDE implementation is based upon the Spyglass SDI spec, which mandates...

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 167826 - Last Review: May 1, 1999 - Revision: 1.0

PRB: DDE with Internet Explorer Doesn't Work As Expected

This article was previously published under Q167826

On This Page

SYMPTOMS

When executing a DDE transaction with Internet Explorer (16-bit or 32- bit), Internet Explorer does not seem to communicate to the application as expected.

CAUSE

Internet Explorer's DDE implementation is based upon the Spyglass SDI spec, which mandates that all specified quoted strings use the \" character combination. Not correctly prefixing a string with the \" character combination when IE expects a quoted string, could cause this problem.

RESOLUTION

When specifying a quoted string, whether as an application, topic, item name, or as an argument, always use the \" character combination.

STATUS

This behavior is by design.

MORE INFORMATION

The Spyglass SDI specification defines a standard notation to indicate argument types. Specifically, all names prefixed with qs, indicating a quoted string, should use the \" character combination to embed a quote character within a quoted string.

To obtain more information on the standard notation for various other argument types, please refer to the "Notation" section of the Spyglass SDI specification.

Steps to Reproduce Behavior

  1. Establish a DDE communication with Internet Explorer, specifying the following:
    application Name: iexplore
    topicName:        WWW_RegisterURLEcho
    						
  2. Note how the Spyglass SDI specification specifies the arguments for this particular topic:
    RegisterURLEcho ( TO Web browser )
    Topic: WWW_RegisterURLEcho
    Item: qsApplication
    Transaction: XTYP_REQUEST
    Data: bSuccess
    						
    Note how the ItemName specified is prefixed with qs, indicating a quoted string, as described above.
  3. Set up an XTYP_REQUEST transaction with DdeClientTransaction, specifying:
    itemName: \"DDESERVER\"
    						
    This should cause the DDESERVER application to be notified of URLEcho events, as specified in the Spyglass SDI specification. Note That incorrectly specifying "DDESERVER" without the \" character combination required of quoted strings causes no such notifications to be sent to the DDESERVER application.
For the WWW_OpenUrl topic, where specifying a URL string should cause IE to navigate to the specified URL, incorrectly specifying the string (that is, without the expected \" character combination) causes IE to not interpret the parameters correctly, thereby not causing it to navigate to the URL.

For additional information, please see the following article in the Microsoft Knowledge Base:
160957  (http://kbalertz.com/Feedback.aspx?kbNumber=160957/EN-US/ ) DDE with Internet Explorer

APPLIES TO
  • Microsoft Internet Explorer 3.0
  • Microsoft Internet Explorer 3.01
  • Microsoft Internet Explorer 3.02
  • Microsoft Internet Explorer 4.0 128-Bit Edition
Keywords: 
kbprb KB167826
Retired KB ArticleRetired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate