Difference between revisions of "Activity:CreateOLEQueryScope (Activity)"
| (9 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| + | The CreateOLEQueryScope Activity provides access to a tables/views within an OLE compliant database by defining a SQL statement. It is typically nested within [[Activity:CreateOLESQLScope (Activity)|CreateOLESQLScope]] or [[Activity:CreateOLEOracleScope (Activity)|CreateOLEOracleScope]]. | ||
| + | |||
| + | =Description= | ||
{{ActivityInfoBox | {{ActivityInfoBox | ||
| title = Create OLE Query Scope | | title = Create OLE Query Scope | ||
| Line 10: | Line 13: | ||
}} | }} | ||
| − | + | ===Arguments=== | |
| − | + | ||
| − | ==Arguments== | + | |
{| class="wikitable sortable" | width = "50%" | {| class="wikitable sortable" | width = "50%" | ||
| Line 29: | Line 30: | ||
|} | |} | ||
| − | ==Usage== | + | ===Usage=== |
This activity is used to access a table(s) or view(s) within a valid OLE DB Scope. The data access is defined by a dtabase SQL Statement. | This activity is used to access a table(s) or view(s) within a valid OLE DB Scope. The data access is defined by a dtabase SQL Statement. | ||
| Line 36: | Line 37: | ||
In the case of a more complex statement where you include more than one table (example: SELECT * FROM TABELE1, TABELE2 where TABELE1.PK = TABELE2.pk ....) then you have to define a unique tablename defining the access indicator for the OLE system. | In the case of a more complex statement where you include more than one table (example: SELECT * FROM TABELE1, TABELE2 where TABELE1.PK = TABELE2.pk ....) then you have to define a unique tablename defining the access indicator for the OLE system. | ||
| − | + | =Example= | |
| − | The CreateOLEQueryScope activity, as used in the larger example "Read MetaClass names from UBIK database": | + | The CreateOLEQueryScope activity, as used in the larger example "Read MetaClass names from UBIK database".<br /> |
| + | [[File:UI_Activity_CreateOLEQueryScope.PNG|border|x700px|CreateOLEQueryScope]] | ||
| − | + | <headertabs /> | |
==See also== | ==See also== | ||
* [[Workflow Designer]] | * [[Workflow Designer]] | ||
| − | * [[ | + | * [[Activity:CreateOLESQLScope (Activity)]] |
| + | * [[Activity:CreateOLEOracleScope (Activity)]] | ||
[[Category:OLE]] | [[Category:OLE]] | ||
| − | |||
Latest revision as of 15:45, 23 February 2015
The CreateOLEQueryScope Activity provides access to a tables/views within an OLE compliant database by defining a SQL statement. It is typically nested within CreateOLESQLScope or CreateOLEOracleScope.
Description
| Create OLE Query Scope | |
|---|---|
| Name | CreateOLEQuery |
| Purpose | Access database data via OLE |
| Category | UBIK Data Exchange |
| Returns | True if successful |
| Version | 2.4.1+ |
Arguments
| Argument | Type | Direction | Purpose |
|---|---|---|---|
| DisplayName | String | In | The display name of the activity |
| Tablename | String | In | The unique tablename of the statement |
| SQLStatement | String | In | The database statement |
| Rows | IEnumerable<DataRow> | Out | A list of all rows of the table |
| Result | Boolean | Out | True if successful, false if failed |
Usage
This activity is used to access a table(s) or view(s) within a valid OLE DB Scope. The data access is defined by a dtabase SQL Statement.
Tablename
If you are accessing a single table with the statement (example: SELECT * FROM TABELE1), then the table name is optional. In the case of a more complex statement where you include more than one table (example: SELECT * FROM TABELE1, TABELE2 where TABELE1.PK = TABELE2.pk ....) then you have to define a unique tablename defining the access indicator for the OLE system.
Example
The CreateOLEQueryScope activity, as used in the larger example "Read MetaClass names from UBIK database".
