Title | Contents | Previous | Next | Index

Appendix B

ADO Methods and Properties

This appendix contains the following information on developing ADO data consumer and data provider applications for Connect ADO:

Using ADO Methods in Connect ADO

Connect ADO supports most of the standard methods for the ADO objects. These methods correspond to the OLE DB interfaces that Connect ADO supports.

Some OLE DB interfaces are required by ADO. ADO uses other interfaces if they are available. Table B-1 defines the use of the supported OLE DB interfaces by ADO.

Table B-1. Use of Supported OLE DB Interfaces in by ADO 

OLE DB Interface

Use of Interface by ADO

IAccessor

Required

IColumnsInfo

Required

IColumnsRowset

If available

ICommand

If available

ICommandPrepare

If available

ICommandProperties

If available

ICommandText

If available

ICommandWithParameters

If available

IConnectionPointContainer

IConvertType

Required

IDBCreateCommand

If available

IDBCreateSession

Required

IDBInfo

If available

IDBInitialize

Required

IDBProperties

Required

IDBSchemaRowset

If available

IErrorInfo

If available

IErrorLookup

If available

IErrorRecords

If available

IGetDataSource

Not used by ADO

IOpenRowset

Required

IParseDisplayName

IPersist

IPersistFile

IRowset

Required

IRowsetChange

If available

IRowsetIdentity

Not used by ADO

IRowsetInfo

Required

IRowsetLocate

If available

IRowsetRefresh

If available

IRowsetResynch

If available

IRowsetScroll

If available

ISessionProperties

Not used by ADO

ISourcesRowset

Required

ISupportErrorInfo

Not used by ADO

ITableDefinition

If available (ADO 2.5)

ITransaction

If available

ITransactionJoin

Not used by ADO

ITransactionLocal

If available

ITransactionObject

Not used by ADO

ITransactionOptions

Not used by ADO

Table B-2 maps the methods used by each ADO object to the supported OLE DB interfaces. When Connect ADO does not support an OLE DB interface, the corresponding ADO method has been omitted.

Table B-2. Mapping Methods Supported by Connect ADO 

ADO Method

ADO Object

OLE DB Interface

AddNew

Recordset

IRowsetChange::InsertRow

BeginTrans

Connection

ITransactionLocal::StartTransaction

Cancel

Command

Connection

Recordset

None

CancelUpdate

Recordset

None

Clone

Recordset

IRowsetLocate

Close

Connection

Close

Recordset

IAccessor::ReleaseAccessor

IRowset::ReleaseRows

CommitTrans

Connection

ITransactionLocal::Commit

Delete

Recordset

IRowsetChange::DeleteRows

Execute

Command

ICommand::Execute

Execute

Connection

ICommand::Execute or

IOpenRowset::OpenRowset

GetRows

Recordset

IAccessor::CreateAccessor

IRowsetLocate::GetRowsAt

IRowset::GetNextRows and

IRowset::GetData

Move

Recordset

IRowsetLocate::GetRowsAt or

IRowset::GetNextRows

MoveFirst

Recordset

IRowsetLocate::GetRowsAt

IRowset::RestartPosition

MoveLast

Recordset

IRowsetLocate::GetRowsAt

MoveNext

Recordset

IRowsetLocate::GetRowsAt

IRowset::GetNextRows

MovePrevious

Recordset

IRowsetLocate::GetRowsAt

IRowset::GetNextRows

Open

Connection

IDBInitialize::Initialize

IDBCreateSession::Create Session

Open

Recordset

IOpenRowset::OpenRowset or

ICommand::Execute

OpenSchema

Connection

IDBSchemaRowset::GetRowset

Requery

Recordset

IOpenRowset::OpenRowset

ICommand::Execute

Resync

Recordset

IRowsetRefresh::RefreshVisibleData

RollBack

Connection

ITransactionLocal::Abort

Supports

Recordset

IRowsetInfo::GetProperties

Update

Recordset

IRowsetChange::SetData

Defining ADO Properties for Connect ADO Data Providers

The Connect ADO data providers use dynamic ADO properties to define functionality. The values of these dynamic properties can be changed or defined. For example, you can specify the data source that the data provider uses at initialization. Most of these dynamic properties map directly to OLE DB properties described in the Microsoft OLE DB programming documentation.

The ADO Connection object represents a single session with an ADO data source. It defines a physical connection to the data source for an ADO data provider and can include user ID, password, and other information. The properties used by the Connection object correspond to OLE DB properties in the Data Source, Data Source Information, Initialization, and Session property groups.

The ADO Command object is the definition of a specific command that you intend to execute against a data source. You can use a Command object to query a database and return records in a Recordset object, or to manipulate the structure of a database.

Table B-3 provides the properties that the Connect ADO data providers support. For more information, refer to the Microsoft OLE DB programming documentation.

Table B-3. Supported Properties of ADO Objects 

Property ID and Object Type

Description and Default

Access Order
Command Object

VALUE=0. For the Command object, columns must be accessed in sequential order determined by the column ordinal.

  • Informix data provider
  • Oracle data provider
  • Sybase data provider
  • XML data provider

Access Order
Recordset Object

VALUE=2. The Recordset object can access columns in any order.

Active Sessions
Connection Object

VALUE=0. There is no limit to the number of sessions that can exist at one time.

Asynchable Abort
Connection Object

VALUE=False. The data provider cannot abort transactions asynchronously.

Asynchable Commit
Connection Object

VALUE=False. The data provider cannot commit transactions asynchronously.

Autocommit Isolation Levels
Connection Object

VALUE=4096. The Oracle data provider and Sybase data provider support:

  • DBPROPVAL_TI_CURSORSTABILITY
  • DBPROPVAL_TI_READCOMMITTED

    VALUE=1052928. The Informix data provider supports:

  • DBPROPVAL_TI_READUNCOMMITTED
  • DBPROPVAL_TI_READCOMMITTED
  • DBPROPVAL_SERIALIZABLE
  • DBPROPVAL_TI_BROWSE
  • DBPROPVAL_TI_CURSORSTABILITY
  • DBPROPVAL_TI_ISOLATED

Blocking Storage Objects
Command Object

VALUE=False. Instantiated storage objects do not prevent the use of other methods.

Bookmark Information
Command Object, Recordset Object

VALUE=0. Bookmark values are specific to this rowset and are not guaranteed to return the same values in other rowsets.

Bookmark Type
Command Object, Recordset Object

VALUE=1. The bookmark type is numeric.

  • XML data provider

Bookmarks Ordered
Command Object, Recordset Object

VALUE=True. Bookmarks can be compared byte-by-byte.

  • XML data provider

Catalog Location
Connection Object

VALUE=1. The catalog name is at the start of the fully qualified name.

  • Informix data provider
  • Sybase data provider
  • XML data provider

    VALUE=2. The catalog name is at the end of the fully qualified name.

  • Oracle data provider. This property is supported only if EnableOracleLinks is set to on.

Catalog Term
Connection Object

Specifies the name the data source uses for a catalog.

VALUE="Database"

  • Informix data provider
  • Oracle data provider
  • Sybase data provider

    VALUE="Directory"

  • XML data provider

Catalog Usage
Connection Object

VALUE=1. Catalog names are supported in all DML statements.

  • Informix data provider
  • Oracle data provider
  • Sybase data provider
  • XML data provider

    NOTE: For the Oracle data providers, this property is supported only when Enable Oracle Links is set to on.

Change Inserted Rows
Command Object, Recordset Object

VALUE=False. DeleteRows returns a status of DBROWSTATUS_E_NEWLYINSERTED for newly inserted rows, and SetData returns DB_E_NEWLYINSERTED.

  • Informix data provider
  • Oracle data provider
  • Sybase data provider

    VALUE=True. The consumer can call IRowsetChange::DeleteRows or IRowsetChange::SetData for newly inserted rows.

  • XML data provider

Column Definition
Connection Object

VALUE=1. Columns can be created non-nullable.

  • Informix data provider
  • Oracle data provider
  • Sybase data provider
  • XML data provider

Column Privileges
Command Object, Recordset Object

VALUE=True. Access rights are restricted on a column-by-column basis.

  • Informix data provider

    VALUE=False. Access rights are not restricted on a column-by-column basis.

  • Oracle data provider
  • Sybase data provider
  • XML data provider

Command Timeout

VALUE=30. Specifies the time, in seconds, to wait for initialization to complete.

  • Sybase data provider

Connect Timeout
Connection Object

Specifies the time, in seconds, to wait for initialization to complete.

VALUE=15

  • Sybase data provider

COM Object Support

Connection Object

VALUE=1. The data provider supports access to BLOBs as structured storage objects.

Connection Status
Connection Object

VALUE=1. The data source is in an initialized state.

Current Catalog
Connection Object

The name of the current catalog.

NOTE: The Oracle data providers do not support this property.

Data Source Name
Connection Object

Specifies the name of the data source (server) used during the connection process. The data source is defined in the DataDirect Technologies Configuration Manager.

Data Source Object Threading Model
Connection Object

VALUE=1. The data provider supports the free-threading model.

Data Source
Connection Object

Specifies the name of the data source or enumerator to which to connect.

DBMS Name
Connection Object

Specifies the name of the product accessed by the data provider.

  • Informix data provider
    VALUE="Informix"
  • Oracle7 data data provider
    VALUE="Oracle"
  • Oracle8 data provider, connecting to an Oracle8 server
    VALUE="Oracle 8"
  • Oracle8 data provider, connecting to an Oracle7 server
    VALUE="Oracle"
  • Sybase data provider
    VALUE="SQL Server"
  • XML data provider
    VALUE="XML 1.0 for Win32"

DBMS Version
Connection Object

Specifies the version of the product that the data provider is currently accessing.

Defer Column
Command Object, Recordset Object

VALUE=False. The data in the column is fetched when the row containing it is fetched.

  • XML data provider

Delay Storage Object Updates
Command Object, Recordset Object

VALUE=True. In delayed update mode, storage objects are also used in delayed update mode.

  • XML data provider

Extended Services
Connection Object

A data provider-specific string that contains extra initialization information. For information on using the provider string, see the "Setting Data Source Properties at Connection Time" for each data provider.

Consumers should use this property only for data provider-specific connection information.

Fetch Backward
Command Object, Recordset Object

VALUE=False. cRows must be non-negative.

  • Informix data provider
  • Oracle data provider
  • Sybase data provider
  • XML data provider

Group By Support
Connection Object

VALUE=2. The GROUP BY clause must contain all of the nonaggregated columns in the select list. It cannot contain any other columns.

Heterogeneous Table Support
Connection Object

VALUE=0. The data provider cannot join tables from different catalogs or data providers.

  • Oracle7 data provider
  • XML data provider

    VALUE=1. The data provider can join tables from different catalogs.

  • Informix data provider
  • Oracle8 data provider
  • Sybase data provider

Hidden Column Count
Command Object, Recordset Object

VALUE=0. The data provider does not hide any rows "hidden" to uniquely identify rows within the rowset.

Hold Rows
Command Object, Recordset Object

VALUE=True. The consumer can retrieve more rows or change the next fetch position while holding previously fetched rows with pending changes.

  • Informix data provider
  • Oracle data provider
  • XML data provider

    VALUE=False. The rowset might require pending changes to be transmitted to the data store before fetching additional rows.

  • Sybase data provider

IAccessor
Command Object, Recordset Object

VALUE=True

IColumnsInfo
Command Object, Recordset Object

VALUE=True

IColumnsRowset
Command Object, Recordset Object

VALUE=True

IConvertType
Command Object, Recordset Object

VALUE=True

Identifier Case Sensitivity
Connection Object

VALUE=2. Case identifiers in SQL are case-insensitive and are stored in lower case in the system catalog.

  • Informix data provider

    VALUE=1. Case identifiers in SQL are case-sensitive and are stored in upper case in the system catalog.

  • Oracle data provider

    VALUE=4. Case identifiers in SQL are case-sensitive and are stored in mixed case in the system catalog.

  • Sybase data provider

    VALUE=8. Identifiers in SQL are case-insensitive and are stored in mixed case in the system catalog.

  • XML data provider

Immobile Rows
Command Object, Recordset Object

VALUE=True. The rowset will not reorder inserted or updated rows.

  • XML data provider

Initial Catalog
Connection Object

Specifies the name of the initial, or default, catalog to use when connecting to the data source.

  • For the XML data provider, this specifies the name of the initial or URL directory that contains HMTL and XML files. Schema rowsets look in this location to find tables.

  • The Oracle data provider supports this property only when Enable Oracle Links is enabled.

IRowsetChange
Command Object

VALUE=False

IRowsetChange
Recordset Object

VALUE=True

IRowset
Command Object, Recordset Object

VALUE=True

IRowsetIdentity
Command Object, Recordset Object

VALUE=True

IRowsetInfo
Command Object, Recordset Object

VALUE=True

IRowsetLocate
Command Object, Recordset Object

VALUE=True

IRowsetScroll
Recordset Object

VALUE=False. Data consumers cannot fetch rows at approximate positions in the rowset.

Isolation Levels
Connection Object

VALUE=1052672. The Oracle data provider supports the following transaction isolation levels:

  • DBPROPVAL_TI_CURSORSTABILITY
  • DBPROPVAL_TI_ISOLATED
  • DBPROPVAL_TI_READCOMMITTED
  • DBPROPVAL_TI_SERIALIZABLE

    VALUE=1052928. The Informix data provider and Sybase data provider support the following transaction isolation levels:

  • DBPROPVAL_TI_BROWSE
  • DBPROPVAL_TI_CURSORSTABILITY
  • DBPROPVAL_TI_ISOLATED
  • DBPROPVAL_TI_READCOMMITTED
  • DBPROPVAL_TI_READUNCOMMITTED
  • DBPROPVAL_TI_SERIALIZABLE

    VALUE=0. The XML data provider does not support transaction isolation levels.

Isolation Retention
Connection Object

VALUE=0. The data provider supports no transaction isolation retention levels.

ISupportErrorInfo
Command Object, Recordset Object

VALUE=True

Literal Bookmarks

VALUE=True. Bookmarks can be compared literally.

  • XML data provider

Literal Bookmarks
Recordset Object

VALUE=True. Bookmarks can be compared literally.

Literal Row Identity

VALUE=False. The consumer must call IRowsetIdentity::IsSameRow to determine whether two row handles point to the same row.

Locale Identifier
Connection Object

Specifies the preferred locale ID for the consumer.

Lock Mode
Command Object, Recordset Object

VALUE=1. The data provider is not required to lock rows to ensure successful updates.

Maximum Index Size
Connection Object

Specifies the maximum number of bytes allowed in the combined columns of an index.

VALUE=0. There is no limit on the index size.

  • Oracle data provider
  • Sybase data provider

    VALUE=255

  • Informix data provider

Maximum Open Chapters
Connection Object

VALUE=0. There is no limit on the number of open chapters or the data provider does not support open chapters.

Maximum Open Rows
Command Object

VALUE=0. There is no limit on the maximum number of rows that can be active at the same time.

Maximum Open Rows
Recordset Object

VALUE=2048. There is no limit on the maximum number of rows that can be active at the same time.

Maximum Pending Rows
Command Object, Recordset Object

VALUE=0. There is no limit on the maximum number of rows that can have pending changes at the same time.

Maximum Row Size Includes BLOB
Connection Object

VALUE=False. The maximum row size does not include the length of all BLOB data.

  • Informix data provider
  • Oracle data provider
  • Sybase data provider
  • XML data provider

Maximum Row Size
Connection Object

VALUE=0. There is no limit on the maximum length.

Maximum Rows
Command Object, Recordset Object

VALUE=0. There is no limit on the maximum number of rows that can be returned in a rowset.

Maximum Tables in SELECT
Connection Object

VALUE=0. There is no limit on the number of tables allowed in the FROM clause of a Select statement.

Memory Usage
Command Object, Recordset Object

VALUE=0. There is no limit on the amount of memory that the rowset can use.

Mode
Connection Object

VALUE=1. The default is read-only.

  • XML data provider

    VALUE=3. The default access is read-write.

  • Informix data provider
  • Oracle data provider
  • Sybase data provider

Multiple Connections
Connection Object

VALUE=True. The data provider silently creates additional connections as required in order to support concurrent command, session, and rowset objects.

  • Sybase data provider

Multiple Parameter Sets
Connection Object

VALUE=True. The data provider supports multiple parameter sets.

  • Informix data provider
  • Oracle data provider
  • Sybase data provider

Multiple Results
Connection Object

VALUE=1. The data provider supports multiple results objects.

  • Informix data provider
  • Oracle data provider
  • Sybase data provider

Multiple Storage Objects
Connection Object

VALUE=True. The data provider supports more than one open storage object at a time.

Multi-Table Update
Connection Object

VALUE=False. The data provider cannot update rowsets derived from multiple tables.

Null Collation Order
Connection Object

VALUE=2. The data provider sorts nulls at the high end of the list.

  • Informix data provider
  • Oracle data provider
  • Sybase data provider
  • XML data provider

NULL Concatenation Behavior
Connection Object

VALUE=1. The result is null valued.

Objects Transacted

VALUE=True. Any object created on the specified column is transacted.

  • Informix data provider

OLE DB Services
Connection Object

Value=-3. The data provider enables all services except automatic transaction enlistment in a Microsoft Transaction Server environment.

  • Oracle7 data provider
  • Sybase data provider (if MTS is not supported)
  • XML data provider

    Value=-1. The data provider enables all services.

  • Informix data provider
  • Oracle8 data provider
  • Sybase data provider (if MTS is supported)

OLE DB Version
Connection Object

Refer to the README file for the supported version of OLE DB.

Open Rowset Support
Connection Object

VALUE=0. The data provider supports opening tables through IOpenRowset.

ORDER BY Columns in Select List
Connection Object

VALUE=False. Columns in an Order By clause do not have to be in the Select list.

Others' Changes Visible
Command Object, Recordset Object

VALUE=False. The rowset cannot see updates and deletes made by others.

Others' Inserts Visible
Command Object, Recordset Object

VALUE=False. The rowset cannot see rows inserted by others.

Output Parameter Availability
Connection Object

VALUE=1. Output parameters are not supported.

  • Informix data provider
  • Oracle8 data provider
  • XML data provider

    VALUE=2. Output parameter values become available at execution.

  • Oracle7 data provider

    VALUE=4. Output parameter values become available when the row is released.

  • Sybase data provider

Own Changes Visible
Command Object, Recordset Object

VALUE=False. The rowset cannot see updates and deletes made by consumers of the rowset unless the command is executed again.

  • Informix data provider
  • Oracle data provider
  • Sybase data provider

    VALUE=True. The rowset can see its own updates and deletes.

  • XML data provider

Own Inserts Visible
Recordset Object

VALUE=False. The rowset can see the rows inserted by consumers only after the command is run again.

Pass By Ref Accessors
Connection Object

VALUE=False. The data provider does not support the DBACCESSOR_PASSBYREF flag.

Password
Connection Object

Specifies the password to be used for connecting to the data source or enumerator.

Persist Security Info
Connection Object

VALUE=False. The data source object cannot store the password or other sensitive authentication information.

Persistent ID Type
Connection Object

VALUE=4. The data provider uses this type of DBID when storing (persisting) DBIDs for tables and columns.

  • XML data provider

Prepare Abort Behavior
Connection Object

VALUE=2. Aborting a transaction preserves prepared commands.

  • Oracle data provider

    VALUE=1. Aborting a transaction deletes prepared commands.

  • Informix data provider
  • Sybase data provider

Prepare Commit Behavior
Connection Object

VALUE=2. Committing a transaction preserves prepared commands.

  • Oracle data provider

    VALUE=1. Committing a transaction deletes prepared commands.

  • Informix data provider
  • Sybase data provider

Preserve on Abort
Command Object, Recordset Object

VALUE=False. After aborting a transaction, the only operations allowed on a rowset are to release row handles, accessor handles, and the rowset.

Preserve on Commit
Command Object, Recordset Object

VALUE=True. After committing a transaction, the rowset remains active.

  • Oracle data provider
  • Sybase data provider

    VALUE=False. After committing a transaction, the rowset can only release row and accessor handles and to release the rowset.

  • Informix data provider

Procedure Term
Connection Object

Specifies a character string that contains the data source's name for a procedure.

VALUE=Procedure

  • Informix data provider

    VALUE=PL/SQL

  • Oracle data provider

    VALUE=Stored Procedure

  • Sybase data provider

Prompt
Connection Object

VALUE=4. Display the dialog box only if additional information is needed.

  • Informix data provider
  • Oracle data provider
  • Sybase data provider
  • XML data provider

Provider Friendly Name
Connection Object

Specifies the name of the data provider, for example, DataDirect Oracle7 ADO Provider.

Provider Name
Connection Object

Specifies the filename of the Connect ADO data provider, where xxx is the identifier for the data provider, and nn is the release level of the data provider. Refer to the README file for the specific file name of the data provider.

VALUE=inxxxnn.DLL

Provider Version
Connection Object

Specifies the version of the data provider.

Quick Restart
Command Object

VALUE=True. IRowset::RestartPosition is relatively quick to execute. It does not require that the command that created the rowset be executed again.

Quick Restart
Recordset Object

VALUE=True. RestartPosition is expensive to execute and requires that the command that created the rowset be executed again.

Quoted Identifier Sensitivity
Connection Object

VALUE=1. Case identifiers for the data provider are case-sensitive and are stored in mixed case in the system catalog.

  • Informix data provider
  • Oracle data provider
  • Sybase data provider

Read-only Data Source
Connection Object

VALUE=False. The data source can be updated.

Remove Deleted Rows
Command Object, Recordset Object

VALUE=False. Static cursors do not remove deleted rows.

  • Informix data provider
  • Oracle data provider
  • Sybase data provider

    VALUE=True. Static cursors remove deleted rows.

  • XML data provider

Report Multiple Changes
Command Object, Recordset Object

VALUE=False. An update or delete cannot affect multiple rows.

  • Informix data provider
  • Oracle data provider
  • Sybase data provider

Return Pending Inserts
Command Object, Recordset Object

VALUE=False. The methods that fetch rows cannot return pending insert rows.

  • Informix data provider
  • Oracle data provider
  • Sybase data provider

Row Privileges
Command Object, Recordset Object

VALUE=False. Access rights are not restricted on a row-by-row basis.

Row Threading Model
Command Object, Recordset Object

VALUE=1. The data provider uses the free-threaded model.

Rowset Conversions On Command
Connection Object

VALUE=True. Callers can inquire on a command about conversions supported on rowsets generated by the command.

Schema Term
Connection Object

Specifies the name the data source uses for a schema.

VALUE=Owner

  • Informix data provider
  • Sybase data provider

    VALUE=User Name

  • Oracle data provider

Schema Usage
Connection Object

VALUE=15. Schema names can be used in text commands in a combination of the following:

  • DBPROPVAL_SU_DML_STATEMENTS
  • DBPROPVAL_SU_TABLE_DEFINITION
  • DBPROPVAL_SU_INDEX_DEFINITION
  • DBPROPVAL_SU_PRIVILEGE_DEFINITION

Scroll Backward
Command Object, Recordset Object

VALUE=False. IRowsOffset must be non-negative.

  • Informix data provider
  • Oracle data provider
  • Sybase data provider
  • XML data provider

Server Cursor
Command Object, Recordset Object

VALUE=False. The data provider determines where to locate the cursor.

Skip Deleted Bookmarks
Command Object, Recordset Object

VALUE=False. GetRowsAt, GetApproximatePosition, or FindNextRow returns DB_E_BADBOOKMARK.

  • Informix data provider
  • Oracle data provider
  • Sybase data provider

    VALUE=True. GetRowsAt, GetApproximatePosition, or FindNextRow skips the bookmark row and continues with the next row.

  • XML data provider

SQL Support
Connection Object

VALUE=275. The Informix data provider, Sybase data provider, and Oracle7 data provider support the following levels of SQL grammar:

  • DBPROPVAL_SQL_ODBC_CORE
  • DBPROPVAL_SQL_ODBC_MINIMUM
  • DBPROPVAL_SQL_ESCAPECLAUSES
  • DBPROPVAL_SQL_ANSI92_ENTRY

    VALUE=19. The Oracle8 data provider supports the following levels of SQL grammar:

  • DBPROPVAL_SQL_ODBC_MINIMUM
  • DBPROPVAL_SQL_ODBC_CORE
  • DBPROPVAL_SQL_ANSI92_ENTRY

    VALUE=0. The XML data provider does not support SQL grammar.

Strong Row Identity
Command Object

VALUE=False. There is no guarantee that the handles of newly inserted rows can be compared successfully.

  • Informix data provider
  • Oracle data provider
  • Sybase data provider

    VALUE=True. The handles of newly inserted rows can be compared successfully.

  • XML data provider

Strong Row Identity
Recordset Object

VALUE=True. The handles of newly inserted rows can be compared successfully.

Structured Storage
Connection Object

VALUE=1. The data provider supports DBPROPVAL_SS_ISEQUENTIALSTREAM.

Subquery Support
Connection Object

VALUE=31. The Informix data provider, Oracle data provider, and Sybase data provider support a combination of zero or more of the following predicates in text commands for subqueries:

  • DBPROPVAL_SQ_CORRELATEDSUBQUERIES
  • DBPROPVAL_SQ_EXISTS
  • DBPROPVAL_SQ_IN

Table Term
Connection Object

Specifies the name the data source uses for a table.

VALUE="Table"

  • Informix data provider
  • Oracle data provider
  • Sybase data provider

    VALUE="File"

  • XML data provider

Transaction DDL
Connection Object

VALUE=8. Transactions can contain DDL and DML statements in any order.

  • Informix data provider

    VALUE=2. Transactions can only contain SQL Data Manipulation Language (DML) statements.

  • Oracle data provider

    VALUE=16. Transactions can contain both DML and table or index modifications, but modifying a table or index within a transaction causes the table or index to be locked until the transaction completes.

  • Sybase data provider

    VALUE=0. The data provider does not support transactions.

  • XML data provider

Unique Rows
Command Object, Recordset Object

VALUE=False. Rows in the rowset may or may not be uniquely identified by their column values.

Updatability
Command Object, Recordset Object

Value=0

Use Bookmarks
Command Object, Recordset Object

VALUE=False. The rowset does not support bookmarks.

  • Informix data provider
  • Oracle data provider
  • Sybase data provider

    VALUE=True. The rowset supports bookmarks.

  • XML data provider

User ID
Connection Object

Specifies the User ID to be used for connecting to the data source.

User Name
Connection Object

Specifies a character string with the name used in a particular database. This can be different from the login name.

Window Handle
Connection Object

Specifies the window handle to use if the data source object or enumerator needs to prompt for additional information.



Title | Contents | Previous | Next | Index

Connect ADO User's Guide and Reference

© 2002, DataDirect Technologies. All rights reserved.