The DdeNameService function registers or unregisters the service names a dynamic data exchange (DDE) server supports. This function causes the system to send XTYP_REGISTER or XTYP_UNREGISTER transactions to other running Dynamic Data Exchange Management Library (DDEML) client applications.
A server application should call this function to register each service name that it supports and to unregister names it previously registered but no longer supports. A server should also call this function to unregister its service names just before terminating.
HDDEDATA DdeNameService(
DWORD idInst, |
// instance identifier |
HSZ hsz1, |
// handle to service name string |
HSZ hsz2, |
// reserved |
UINT afCmd |
// service name flags |
); |
Flag |
Meaning |
DNS_REGISTER |
Registers the error code service name. |
DNS_UNREGISTER |
Unregisters the error code service name. If the hsz1 parameter is 0L, all service names registered by the server will be unregistered. |
DNS_FILTERON |
Turns on service name initiation filtering. The filter prevents a server from receiving XTYP_CONNECT transactions for service names it has not registered. This is the default setting for this filter. |
If a server application does not register any service names, the application cannot receive XTYP_WILDCONNECT transactions. | |
DNS_FILTEROFF |
Turns off service name initiation filtering. If this flag is specified, the server receives an XTYP_CONNECT transaction whenever another DDE application calls the DdeConnect function, regardless of the service name. |
If the funcion succeeds, it returns a nonzero value. That value is not a true HDDEDATA value, merely a Boolean indicator of success. The function is typed HDDEDATA to allow for possible future expansion of the function and a more sophisticated return value.
If the function fails, the return value is 0L.
The DdeGetLastError function can be used to get the error code, which may be one of the following values:
DMLERR_DLL_NOT_INITIALIZED
DMLERR_DLL_USAGE
DMLERR_INVALIDPARAMETER
DMLERR_NO_ERROR
The service name identified by the hsz1 parameter should be a base name (that is, the name should contain no instance-specific information). The system generates an instance-specific name and sends it along with the base name during the XTYP_REGISTER and XTYP_UNREGISTER transactions. The receiving applications can then connect to the specific application instance.
DdeConnect, DdeConnectList, DdeInitialize, XTYP_REGISTER, XTYP_UNREGISTER
file: /Techref/os/win/api/win32/func/src/f14_1.htm, 5KB, , updated: 2000/4/7 12:19, local time: 2024/8/17 12:58,
18.227.114.225:LOG IN
|
©2024 These pages are served without commercial sponsorship. (No popup ads, etc...).Bandwidth abuse increases hosting cost forcing sponsorship or shutdown. This server aggressively defends against automated copying for any reason including offline viewing, duplication, etc... Please respect this requirement and DO NOT RIP THIS SITE. Questions? <A HREF="http://techref.massmind.org/techref/os/win/api/win32/func/src/f14_1.htm"> DdeNameService</A> |
Did you find what you needed? |
Welcome to massmind.org! |
Welcome to techref.massmind.org! |
.