ODBC - OLEDB connection
This section describes the additional
configuration parameters when you plan to use the ODBC connection client. Before
entering this configuration section, make sure you configured the ODBC
driver or created an UDL = Universal
Data Link. You will need to create an udl whenever you plan to use OLEDB
instead of ODBC.
Select ODBC in the connection type listbox when
defining the database connection. Your screen will look like:
- DSN name: (Required) Enter
or select the DSN that points to your ODBC driver. This is the DSN on the
client's machine. This may be a different machine then your configuration
manager is installed on. The listbox only shows the DSNs of the workstation
you are working on. Therefore the DSN you need may not be in the list when
your client is gonna run on a different machine. If your DSN is not in the
list, simply enter the DSN manually.
If you plan to use OLEDB, you don't have to create a DSN. Create a
UDL instead, and enter the full path
to the .udl file in here. Again the path and filename must be seen from the
connection client's workstation point of view.
- Username: (optional) the username to access the database.
- Password: (optional) the password to access the database.
- DB library (user): (optional) SQL prefix to be written in front of
the all tables related to this connection. This might be needed
- when you access the database with a different user then the
database owner, Typical entry would be <database owner>. Example:
if the database owner is 'promes' then all tables can be accessed as
'promes.tablename'. (Do not confuse with MS-Access where attached tables
are using an underscore (_).
- when you must specify the library name where the database resides.
Typical for AS400.
- Control library (user): (optional) Same as DB library, but this
entry points to the PRODBX typical tables (HEAD and TRB) if you enabled the
trigger-based channel. When you created these tables (files) in the same
environment as your main tables, you must make this entry the same as DB
- Polling time normal: (Required) time in milliseconds between 2
consecutive pollings. Or the time between two checkings of the HEAD table,
containing the pointer of the circular buffer of generated triggers.
- Polling time fast: (optional) time in milliseconds for a fast
polling. This time is only enabled when the client gets a transaction of
COMMAND type. This can only be generated by clients directly connected with
the source application, like ADO and XML type connections. These clients are
able to send a command to another client for getting an instant answer of
- Database type: (for future enhancement)
- Tds update function: (optional) Time and date stamp function when
the trigger on the database generates the timestamp when the trigger was
executed (generated the transaction). This timestamp is stored in the TRB
table of the source database in the TDS_UPDATE field, in the format typical
to that database. In this field you select the conversion method for
converting this format to the format of the destination database where the
'Last update on field' is kept.
- TRB field to stack: (optional) You may also define a fieldname you
created in the TRB table, filled by your trigger, of which the contents
should be copied to the STACK as extra input for a function when
interpreting the transaction.