XTYP_EXECUTE transaction
A client uses the XTYP_EXECUTE transaction to send a command string to the server. A Dynamic Data Exchange (DDE) server callback function, DdeCallback, receives this transaction when a client specifies XTYP_EXECUTE in the DdeClientTransaction function.
#define XCLASS_FLAGS 0x4000
#define XTYP_EXECUTE (0x0050 | XCLASS_FLAGS )
Parameters
-
uType
-
The transaction type.
-
uFmt
-
Not used.
-
hconv
-
A handle to the conversation.
-
hsz1
-
A handle to the topic name.
-
hsz2
-
Not used.
-
hdata
-
A handle to the command string.
-
dwData1
-
Not used.
-
dwData2
-
Not used.
Return value
A server callback function should return DDE_FACK if it processes this transaction, DDE_FBUSY if it is too busy to process this transaction, or DDE_FNOTPROCESSED if it rejects this transaction.
Remarks
This transaction is filtered if the server application specified the CBF_FAIL_EXECUTES flag in the DdeInitialize function.
An application must free the data handle obtained during this transaction. An application must, however, copy the command string associated with the data handle if the application must process the string after the callback function returns. An application can use the DdeGetData function to copy the data.
Because most client applications expect a server application to perform an XTYP_EXECUTE transaction synchronously, a server should attempt to perform all processing of the XTYP_EXECUTE transaction either from within the DDE callback function or by returning the CBR_BLOCK return code. If the hdata parameter is a command that instructs the server to terminate, the server should do so after processing the XTYP_EXECUTE transaction.
Requirements
| Requirement | Value |
|---|---|
| Minimum supported client |
Windows 2000 Professional [desktop apps only] |
| Minimum supported server |
Windows 2000 Server [desktop apps only] |
| Header |
|
See also
-
Reference
-
Conceptual