Types of Predefined Actions
OLE DB for OLAP provides for standard actions that have predefined triggering methods. This enables client applications to execute the standard action types without needing to understand the nature of the action. The following table lists the defined action types.
Predefined action types |
Interpretation |
|---|---|
URL |
The returned string in the ACTIONS rowset CONTENT column is a URL that should be launched through an Internet browser. |
HTML |
The returned string in the CONTENT column is an HTML script. The script should be saved to a file and rendered through an Internet browser. The script can be of any format that can be interpreted by the browser ? for example, an .asp file containing scripting language commands. |
STATEMENT |
The string in the CONTENT column contains a statement that is executed by calling ICommandText::SetCommandText and then calling ICommand::Execute. |
DATASET |
The string in the CONTENT column is an MDX statement. As with STATEMENT action types, the statement should be executed on an OLE DB command object by calling ICommandText::SetCommandText and ICommand::Execute. The client application should set the riid parameter in Execute to IID_IMDDataset. |
ROWSET |
Like DATASET, but the client application should call ICommand to return IID_IRowset. |
COMMAND |
The string in the CONTENT column contains an executable file name and, possibly, additional parameters. The client application should execute the command without waiting for its completion. |
PROPRIETARY |
The string in the CONTENT column is in a proprietary format. The client application should not execute the action unless it has custom knowledge of the proprietary format. |