Dynamic Data Exchange Functions (Magic xpa 3.x)
Magic xpa's DDE implementation is done through Magic xpa functions. Every function initiates a complete DDE conversion, and terminates the conversion before it returns. This means that the DDE exchange is a "cold" exchange and it is always initiated by Magic xpa. Magic xpa will not be aware of changes made by other applications and applied to data Magic xpa obtains via a DDE exchange.
The DDE server application must be online for Magic xpa to communicate with it. Trying to access a DDE server from Magic xpa without the server being online will not cause the server to load, and the operation will fail.
The DDE servers do not get focus when accessed by a client application. Therefore, if the Magic xpa DDE functions cause an error in the server application, the server application will respond by issuing an error dialog box,this dialog box will not get focus, and the Magic xpa DDE operation will time-out and fail.
The Magic xpa DDE functions are synchronous. This means that Magic xpa will wait to receive the result of the DDE operation before it continues processing.
Note that DDE functions are not portable. They can be used only under Windows. If you attempt to execute DDE functions under a different operating system DDEGet will always return empty strings; DDEPoke and DDExec will always return FALSE; and DDERR will always return code 15, meaning that a DDE function was executed on an operating system other than Windows.
DDEBegin
DDEEnd
DDEGet
DDEPoke
DDERR
DDExec
