Exception |
Description |
|
An application program specified in a |
|
An application ID specified in a |
|
A format number specified in a |
|
A format string specified in a |
|
The application was unable to initialize DDE communications, which caused a call to the DDE layer to fail. |
|
An invalid parameter, such as a NULL value, is passed to a DDE package routine. |
|
A transaction failed because the server application is busy. |
|
A request for a synchronous data transaction has timed out. |
|
A request for a synchronous execute transaction has timed out. |
|
A parameter failed to be validated. Some of the possible causes are as follows: The application used a data handle initialized with a different item-name handle or clipboard data format than that required by the transaction. The application used an invalid conversation identifier.More than one instance of theapplication used the same object. |
|
A memory allocation failed. |
|
A client's attempt to establish a conversation has failed. The service or topic
name in a |
|
A transaction failed. The item name in a Poke or Request transaction may be in error. |
|
A call is made to the DDE package but DDE is not supported on the current software platform. |
|
A request for a synchronous poke transaction has timed out. |
|
An internal call to the PostMessage function has failed. |
|
The server terminated before completing a transaction. |
|
An internal error has occurred in the DDE layer. |
About the DDE
built-in package
Microsoft Windows predefined data formats
Copyright © 1984, 2005, Oracle. All rights reserved.