Hi Michael

According to the documentation, DDE is no longer supported as a native function in VB.NET as it was in VB6.0 (or VFP)
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vbcon/html/vbcondynamicdataexchangechangesinvisualbasicnet.asp

However, DDE is still a necessary part of the Windows OS and it can still be used by calling Win32API functions (basically SendMessage)
A full explanation can be found at:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winui/WinUI/WindowsUserInterface/DataExchange/DynamicDataExchange/UsingDynamicDataExchange.asp

From a .NET language, you can call API functions via P-Invoke; look at the "Consuming Unmanaged DLL Functions" topic in the .NET Framework Developer's Guide

Of course, if you have a chance to rewrite / wrap your existing code and expose it as COM objects, that would be much better than keeping the old DDE protocol alive; but if you need to mantain it this would be the way to do it.

Hope this helps and bye,
Jose.

>I have some old foxpro apps which act as dde servers, and use this facility to enable automation from other foxpro applications.
>
>I now need to be able to automate these old applications from .Net applications, but have had no luck searching for methods to accomplish this.
>
>In addition, I have tried putting my DDE client code in a foxpro .dll with an olepublic class in it. Although the code does not through up any errors, the DDE auotomation fails to run.
>Does anyone know if this method is viable, because I don't want to spend too long persuing this avenue if Foxpro cannot manage this sort of thing.
>