Hi Ctussey, spacey!<br>
<br>
NetDDE is fairly difficult to use, and definately undocumented. I think Microsoft is actively discouraging it's use (with good reason, IMO) You would be better off using DCOM or writing a sockets application. <br>
<br>
If you're ambitious, here's something to try: Use a Named Pipe to communicate. You can find samples in the MSDN under:<br>
Platfom SDK<br>
Windows Base Services<br>
Interprocess Communication<br>
Pipes<br>
<br>
It handles all the messy lookup functions (finding the other machine, etc), and has a function called TransactNamedPipe which does a write and a read to/from the pipe all in one api call.<br>
<br>
Chip H.<br>