Yes, I know, it's not supported. BUT I'm sure some clever brain has figured
out a mechanism to do so. I have a plethora of VB6 applications that all do
DDE to an application. Yes, the application supports OLE - whoops, another
belt and braces effort! - but it won't support talking to multiple server
applications concurrently, nor, selecting a specific exe: just get the one
your offered - can't persuade them to use the ROT - so I am condemned to
using DDE in order to differentiate between apps using the topic.
So, back to basics, has anyone coerced VB.NET into talking DDE?
Thanks
AG
Theo Verweij - 13 Jul 2006 20:37 GMT
How about building a vb6 activex dll that's handling the DDE
concersations, and call this dll from .NET
> Yes, I know, it's not supported. BUT I'm sure some clever brain has figured
> out a mechanism to do so. I have a plethora of VB6 applications that all do
[quoted text clipped - 9 lines]
>
> AG
Alan Gillott - 17 Jul 2006 12:18 GMT
I thought about that but there are issues. It is already an ActiveX dll and
has to remain so. I might add, a HUGE Activex dll. However the caller is
responsible for providing the form. I don't want to turn it into an activex
exe because that gives me another set of issues to deal with and can break
existing applcations. The nice thing is that is already designed as a class
so if someone has managed to implement the DDE API calls then I could save
myself a headach plus the books I need to define the API are 5000 miles away
and very heavy to carry in an aeroplane I don't plan to catch for several
months.
> How about building a vb6 activex dll that's handling the DDE
> concersations, and call this dll from .NET
[quoted text clipped - 13 lines]
>>
>> AG
Theo Verweij - 17 Jul 2006 20:10 GMT
Maybe this is helpful:
http://www.angelfire.com/biz/rhaminisys/ddclient.html
> I thought about that but there are issues. It is already an ActiveX dll and
> has to remain so. I might add, a HUGE Activex dll. However the caller is
[quoted text clipped - 23 lines]
>>>
>>> AG