LOTUS CONNECTORS


OLE DB Connector Properties
The following table defines the properties for the Lotus® Connector for OLE DB.
TokenName/DescriptionType
LCTOKEN_DATABASEDatabase

Database name

Note This token cannot be used with Microsoft® Access. Rather, use Init_DataSource to specify the path of the Jet (.mdb) database file.

See the Init_DataSource description (Token 3) below for related information.

Text
LCTOKEN_USERIDUser ID/name (Userid)

User ID/ Name used for logging in during connection.

Text
LCTOKEN_PASSWORDPassword

Password. Used for logging in during connection.

Text
LCTOKEN_METADATAObject Class

Data table or view: the source or target for data transfer operations.

Text
LCTOKEN_INDEXIndex

Index name.

Text
LCTOKEN_MAP_NAMEMapByName

Whether to map by name (TRUE) or position (FALSE) when transferring data between data source and target.

Boolean
LCTOKEN_WRITEBACKWriteback

Whether to perform writeback or non-writeback operations. Even with Writeback operations, the fieldlist must contain key fields which uniquely identify the record to be modified.

Boolean
LCTOKEN_FIELDNAMESFieldNames

Text list of fields to select -- used for Select operations.

TextList
LCTOKEN_CONDITIONCondition

OLE DB Provider-specific syntax conditional clause -- used for Select operations.

Text
LCTOKEN_STAMPFIELDStampField

Field name of timestamp field -- used for Select operations.

Text
LCTOKEN_BASESTAMPBaseStamp

Minimum timestamp value to include in results -- used for Select operations.

Datetime
LCTOKEN_MAXSTAMPMaxStamp

During a Select operations, set by the connector to the current timestamp value.

Datetime
LCTOKEN_PROCEDUREProcedure

The stored procedure to execute for the Call method.

Datetime
LCTOKEN_OWNEROwner

Only objects owned by the owner name in this property are included in the result set.

Text
1.00Provider

The OLE DB provider’s COM programmatic ID (ProgID). Thus it indicates which OLE DB driver to use. For Microsoft SQL Server 7 use "SQLOLEDB"; for Microsoft Access 2000 databases use "Microsoft.Jet.OLEDB.4.0" -- Required

Text
2.00Init_Location

Corresponds to the OLE DB DBPROP_INIT_LOCATION property. Not used for either the SQL Server or Jet OLE DB providers.

Text
3.00Init_DataSource

Corresponds to the OLE DB DBPROP_INIT_DATASOURCE property. For the Microsoft SQL Server provider, enter the server name.

For the MS Access Jet provider, use the path to the Jet (.mdb) database.

This is required when using MS Access.

Text
4.00Init_Catalog

Corresponds to the OLE DB DBPROP_INIT_CATALOG property. For the Microsoft SQL Server provider enter the name of the initial database to use. Not used for the Microsoft Jet provider.

Text
5.00Init_Mode

Corresponds to the OLE DB DBPROP_INIT_MODE property. Not used for the Microsoft® SQL Server provider.

For the Microsoft Jet provider, bitwise or the numeric values to indicate special access privileges. The default setting is DB_MODE_READWRITE.

The following list shows the Access Privileges, Value, and Description for each setting.

  • DB_MODE_READ -- 1 -- Indicates read-only
  • DB_MODE_READWRITE -- 3 -- Indicates read/write
  • DB_MODE_SHARE_DENY_WRITE -- 8 -- Prevents others from opening in write mode
  • DB_MODE_SHARE_EXCLUSIVE -- 12 -- Prevents others from opening in read/write mode
  • DB_MODE_SHARE_DENY_NONE -- 16 -- Indicates that neither read nor write access can be denied to others
Integer
6.00Init_ProviderString

Corresponds to the OLE DB DBPROP_INIT_PROVIDERSTRING property. OLE DB recognizes an ODBC-like syntax in provider string property values. Within the string, elements are delimited by using a semicolon. The final element in the string must be terminated with a semicolon. Each element consists of a keyword, an equal sign character, and the value passed on initialization, as shown in the following example:

Server=Gumby;UID=everett;

For the Microsoft SQL Server provider, developers may need to set the network property to the name of the Net-Library (DLL) used to communicate with the SQL Server. The name should not include the path or the .dll file name extension. So for example to use the TCP/IP network library, add the following: "Network=DBMSSOCN;" Alternatively, the default Net-Library can be set by the SQL Server Client Network Utility.

Text
7.00Auth_Integrated

Corresponds to the OLE DB DBPROP_AUTH_INTEGRATED property. Indicates the authentication service to use if any. For the Microsoft SQL Server provide, one can enter "SSPI" in order to use Windows NT Authentication service for authorizing user access to the SQL Server database. If this property is not set, the SQL Server login and password should be specified in the UserID and Password properties.

Not used for the Microsoft Jet provider.

Text
8.00CommitFrequency

Number of data modification actions between commits. A value of zero causes a commit at disconnect; a value of one auto-commits every action; any other value commits after that many data modification actions.

Integer
9.00IsolationLevel

This property determines the extent that outside actions can affect a transaction. Read Committed is the default option.

The following list shows the Name, Description, and Value for each option.

  • Read Uncommitted -- A transaction operating at the Read Uncommitted level can see uncommitted changes made by other transactions. At this level of isolation, dirty reads, nonrepeatable reads, and phantoms are all possible -- 256
  • Read Committed -- A transaction operating at the Read Committed level cannot see changes made by other transactions until those transactions are committed. At this level of isolation, dirty reads are not possible but nonrepeatable reads and phantoms are possible -- 4,096
  • Repeatable Read -- A transaction operating at the Repeatable Read level is guaranteed not to see any changes made by other transactions in values it has already read. At this level of isolation, dirty reads and nonrepeatable reads are not possible but phantoms are possible. -- 65,536
  • Serializable -- A transaction operating at the Serializable level guarantees that all concurrent transactions interact only in ways that produce the same effect as if each transaction were entirely executed one after the other. At this isolation level, dirty reads, nonrepeatable reads, and phantoms are not possible. transactions interact only in ways that produce the same effect as if each transaction were entirely executed one after the other. At this isolation level, dirty reads, nonrepeatable reads, and phantoms are not possible. -- 1,048,576
Integer
10.00TraceSQL

Include all SQL statements generated during the execution of the activity in the activity's log.

Boolean