OK then........ So......... Ummmmmmm.......
What part of Quebec are you from?
Here's a little info I found for everyone:
Q: What is the difference between DDE and NetDDE?
A: DDE and NetDDE are quite different technologies. DDE is the first crack at IPC offered by Microsoft when they decided that their OS was "multi-tasking". The intent was simple transmission of (name,value) pairs, and it was implemented in as simple a manner as they thought possible. It is well established and robust, once you figure out how to implement it correctly. NetDDE is an extension created by Wonderware, the makers of InTouch. It is an attempt to extend the DDE semantics to the network. It does indeed show real problems with more than a few nodes, and everybody who has tried to use it is aware of this.
We don't use NetDDE (the Wonderware mechanism). It is not reliable. We use local DDE (the Microsoft mechanism), which is reliable. The networking portion of our Cascade Connect connection is done using TCP/IP. We carefully handle timeouts, breaks, re-connections, multiple connections, multiple QNX hosts, etc. at the TCP level. Once the message is on the Windows box, it is converted to local (reliable) DDE where it can be transmitted to DDE-aware local processes.
To recap, NetDDE is unreliable. Don't use it. Don't confuse it with DDE either. DDE is old, but it is reliable, fast, and ubiquitous. Given that many programs offer no alternative interface, DDE can be the only viable choice for many applications. Even those programs that do offer an alternative interface usually also offer DDE.