• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 564
  • Last Modified:

DDE Over Network

I'm trying to talk to another application over my Microsoft network.  Application 1 is running all the time on Win 95 and is set up as a DDE Server.  Application 2 is running on a WIN NT Server 4 and I want it to connect via DDE to Application 1.  I believe I need to use NETDDE but can't find any information on it.Any help gratefully received.Darren
0
Dazza051197
Asked:
Dazza051197
  • 2
  • 2
1 Solution
 
wdawesCommented:
Windows NT will automatically start NetDDE when you start an application that requires NetDDE, but, Win95 is different. Do (Find, Files) from Win95 for the following files: nddeapi.dll, nddenb.dll, netdde.exe. (I'm assuming that you are using Microsoft's NetDDE, and not Wondwerware's). Click on netdde.exe to start it, then Ctrl-Alt-Del (task manager) to verify that it is running. If you want netdde.exe to start up automatically when Win95 is started, them copy netdde.exe to the StartUp folder. To test if NetDDE is working correctly between Win95 and Windows NT, use Chat (you may have to install Chat from your Win95 Setup CD, look in the \other directory).
0
 
Dazza051197Author Commented:
NETDDE is definitely running on all the machines on the network, but my application will not find the DDE conversation.  Do I need to do anything different in my code or should it just find it as a normal DDE conversation ?  Will I need to add anything to the registry on any of the machines so it knows which machine application 2 is on ?
0
 
wdawesCommented:
If NetDDE is running on NT, then you can verify this by going to the Services icon, and see that the two services, Network DDE and Network DDE DSDm are starting automatically. And, of course, you've verified that Chat or Hearts works between the two machines in question (highly recommended before proceeding) ...
 
Go to the NT server and run ddeshare.exe. Notice how Chat, Hearts, etc. have entries there. On Win95 you have to hack the registry to set up your DDE shares (actually you can run the WFW 3.11 version of ddeshare on Win95 to see how to set up the registry). Thus, it is easier to use WinNT for your DDE Server.
So you have to add a share for your application: on NT, run ddeshare; click Add a Share; enter your application name, and * for the topic name, in the Old Style box; click the Permissions button, and grant Full Control to Everyone,then OK; now highlight your newly added share for yout application, then click on Trust Share; click all options, and enter a zero forthe Cmd show overide, then OK.

On thing you may want to check in the code of your application is that the when the client INITIATES the first part of the DDE conversation, that the UNC for the server (say NODE2) is included, for example: \\NODE2\your_dde_server|some_topic, this being the DDE syntax \\NODENAME\APPLICATION|TOPIC!ITEM. After the  DDE conversation between NODE1(client) and NODE2(server) starts, the UNC (\\NODENAME or \\NODE2) is not necessary.

For a good primer on this, see http://www.visualautomation.com/info/tcntdde1.htm
 
0
 
Dazza051197Author Commented:
Thats what I was missing, the \\unc\app.  I thought everything would just be transparent, after all, hows my app1 supposed to know it's going to run on a network.  I'll just add a UNC entry to an INI file and leave the user to enter it.  Thanks for the help.Darren
0

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now