Back to Index

 

  The Microsoft™ Access Data Object

The MS Access Data object uses the Jet OleDb driver to read / write data to any MS Access database file.   By entering in the custom Access related properties, the object will automatically build a connect string that will give BlueSky Integration Studio access to the data in the database.   You can also use an MS Access database table as a lookup reference table.

Properties

Action

Describes the action to take for output streams.  Ignored for input streams.  Valid options are:

Option

Description

None

Take no action

ClearThenInsert

Clears the table, then inserts records

InsertOnly

Inserts record into table

UpdateOnly

Updates record only where the specified key columns match

InsertOrUpdate

Attempts to update record where the specified key columns match, if no matching record is found the record is inserted into the table

DeleteOnKeyMatch

Deletes record only where the specified key columns match

Catalog

Database catalog name.  For instance: Northwind.  Some databases do not use the concept of catalogs in which this property should be left blank.

ColumnLayout

The column layout (or file structure) of the table.  Click on the Ellipse (...) button to fill in the column layout, or select an existing column layout from the repository. See also (Column level Write Flags)

CommandTimeout

Specify the maximum number of seconds to wait for any command that is sent to the database.  Once this time is exceeded you will receive a timeout error.

ConnectString

(read only) This property displays the ConnectString that will be used to connect to the data source.  It is built automatically by deriving the information from the other properties.

ConnectStringOtherParams

Any custom parameters to be included in the ConnectString. (example: see OleDb)

CreateTable

The create table property allows you to create your output table in the database during the job execution.  You can also choose to DROP the table prior to creating it.  The create table wizard will also generate your create table statement for you based on the pre-defined ColumnLayout.

DatabaseFileName

The path and file name to the Access database file.

DataProvider

The OleDb Data provider to use specific to the type of database you are using for this object.  Click the ellipse button (...) on the property to get a list of available OleDb drivers on your system.

DateTimeFormat

DateTime format mask to use when loading the data.  This is a useful way to format all columns defined as DateTime to standard format.  It saves you time from having to format each column individually in the Join object.  If the column is left blank the date will be read as it is received from the database.   Click on the ellipse to use the mask builder tool.

RowsPerTransaction

This data object supports batch SQL transactions which can greatly enhance the loading speed of a BlueSky Integration Studio job.  Simply enter the number of SQL statements to place in the internal queue before submitting them to the database.  For instance; by entering 1000 in this property, BlueSky Integration Studio will not attempt to send the sql commands until 1000 records have been read from the input source, or until the last record is read (i.e. if there are only 300 input records, of course it will then write them to the database).   The database can process 1000 sql statements at once, much faster than 1000 individually sent sql statements.  (see also: What is SQL Batching?)

Signon

The user name and password to use to connect to the database.  The password is hidden in this property.  Click the Ellipse (...) button on the property where you can enter both the user name and hidden password.

Tablename

Database table name

Comments

Comment area to give descriptive text about the data object and its purpose.

Alias

Alias identifier.  Aliases are used on all design objects to simplify coding and to ensure each object has a unique identifier.

Name

Descriptive name for this object.  You can enter any text to describe the object

GenerateSql

Yes / No.  By default, the data object will automatically generate the SQL Select statement for you deriving the information from other properties such as the Tablename and ColumnLayout properties.  By changing this property to No you can hand-code the SQL statement in the SQLSelect property window.  This gives you complete flexibility to enter SQL statements that join multiple tables together and/or use database optimizer hints.

OnPostDMLFailure

ContinueOn / AbortJob  : When DML (data manipulation language) statements are entered into the PostDML property, you can control whether your job continues executing if the DML statement fails for some reason.  DML statements include any valid UPDATE, INSERT or DELETE type of SQL statements. (see Pre / Post DML example)

OnPreDMLFailure

ContinueOn / AbortJob  : When DML (data manipulation language) statements are entered into the PreDML property, you can control whether your job continues executing if the DML statement fails for some reason.  DML statements include any valid UPDATE, INSERT or DELETE type of SQL statements. (see Pre / Post DML example)

PostDML

DML (data manipulation language) statement to execute after the job or Join object completes.  Any valid INSERT, UPDATE or DELETE type of SQL Statement. (see Pre / Post DML example)

PreDML

DML (data manipulation language) statement to execute before the job or Join object starts.  Any valid INSERT, UPDATE or DELETE type of SQL Statement. (see Pre / Post DML example)

SQLOutputFile

(output only).  This SQLOutputFile is the path and filename to a file where you want the actual SQL statements being generated to be logged.   This can come in handy when you are trying to debug a job, or some problematic data.  In production it is best to leave this property empty.  For instance: c:\jobsql.log

SQLSelect

The SQL Select statement that will be used for data objects used in input streams.  The SQL statement is built automatically by deriving information from other properties such as the Tablename and ColumnLayout properties.  You can override this SQL Statement by setting the GenerateSQL property to No.

See also:  Handling Dates in MS Access


© 2003 - 2007 Relational Solutions, Inc. - All rights reserved