. "1"^^ . . . . "The fourth dialog enables you to set optional ODBC connection parameters.\r\n\r\nRead-only connection \u2014 Specifies whether the connection is \"Read-only.\" Must be unchecked to INSERT, UPDATE, or DELETE records, and to run some Stored Procedures including some built-in functions. \r\n\r\nDefer fetching of long data \u2014 Defers fetching of LONG (BINARY, BLOB, etc.) fields in wildcard queries. This provides significant performance increases when fields in query do not include LONG data fields. \r\n\r\nDisable interactive login \u2014 Suppresses the ODBC \"Username\" and \"Password\" login dialog boxes when interacting with your ODBC DSN from within an ODBC compliant application.\r\n \r\nRow Buffer Size \u2014 This attribute specifies the number of records to be delivered from the driver to the client application in a single batch. Values can range from 1 to 999.\r\n \r\nMax Rows Override \u2014 Allows you to set a limit for the maximum number of rows to be returned from a query. The default value of 0 means no limit.\r\n \r\nInitial SQL \u2014 Lets you specify a file containing SQL statements that will be run automatically against the database upon connection.\r\n \r\nDynamic Cursor Sensitivity \u2014 Enables or disables the row version cache used with dynamic cursors. When dynamic cursor sensitivity is set high, the Cursor Library calculates checksums for each row in the current rowset and compares these with the checksums (if any) already stored in the row version cache for the same rows when fetched previously. If the checksums differ for a row, the row has been updated since it was last fetched and the row status flag is set to SQL_ROW_UPDATED. The row version cache is then updated with the latest checksums for the rowset. From the user's point of view, the only visible difference between the two sensitivity settings is that a row status flag can never be set to SQL_ROW_UPDATED when the cursor sensitivity is low. (The row status is instead displayed as SQL_ROW_SUCCESS.) In all other respects, performance aside, the two settings are the same. Deleted rows don't appear in the rowset. Updates to the row since the row was last fetched are reflected in the row data, and inserted rows appear in the rowset, if their keys fall within the span of the rowset. If your application does not need to detect the row status SQL_ROW_UPDATED, you should leave the High Cursor Sensitivity checkbox unchecked, as performance is improved. The calculation and comparison of checksums for each row fetched carries an overhead. If this option is enabled, the table oplrvc must have been created beforehand using the appropriate script for the target database. \r\n\r\nEnable logging to the log file \u2014 Check the checkbox and use the associated textbox to provide the full path to a file in which to log diagnostic information.\r\n\r\nClick Next to continue. " . . "Step 1" . . . . "Start a JDBC-compliant application e.g, the JDBC Demo Application bundled with the OpenLink JDBC-ODBC Bridge Driver Installer\n" . "The fourth dialog enables you to set optional ODBC connection parameters.\r\n\r\nRead-only connection \u00E2\u0080\u0094 Specifies whether the connection is \"Read-only.\" Must be unchecked to INSERT, UPDATE, or DELETE records, and to run some Stored Procedures including some built-in functions. \r\n\r\nDefer fetching of long data \u00E2\u0080\u0094 Defers fetching of LONG (BINARY, BLOB, etc.) fields in wildcard queries. This provides significant performance increases when fields in query do not include LONG data fields. \r\n\r\nDisable interactive login \u00E2\u0080\u0094 Suppresses the ODBC \"Username\" and \"Password\" login dialog boxes when interacting with your ODBC DSN from within an ODBC compliant application.\r\n \r\nRow Buffer Size \u00E2\u0080\u0094 This attribute specifies the number of records to be delivered from the driver to the client application in a single batch. Values can range from 1 to 999.\r\n \r\nMax Rows Override \u00E2\u0080\u0094 Allows you to set a limit for the maximum number of rows to be returned from a query. The default value of 0 means no limit.\r\n \r\nInitial SQL \u00E2\u0080\u0094 Lets you specify a file containing SQL statements that will be run automatically against the database upon connection.\r\n \r\nDynamic Cursor Sensitivity \u00E2\u0080\u0094 Enables or disables the row version cache used with dynamic cursors. When dynamic cursor sensitivity is set high, the Cursor Library calculates checksums for each row in the current rowset and compares these with the checksums (if any) already stored in the row version cache for the same rows when fetched previously. If the checksums differ for a row, the row has been updated since it was last fetched and the row status flag is set to SQL_ROW_UPDATED. The row version cache is then updated with the latest checksums for the rowset. From the user's point of view, the only visible difference between the two sensitivity settings is that a row status flag can never be set to SQL_ROW_UPDATED when the cursor sensitivity is low. (The row status is instead displayed as SQL_ROW_SUCCESS.) In all other respects, performance aside, the two settings are the same. Deleted rows don't appear in the rowset. Updates to the row since the row was last fetched are reflected in the row data, and inserted rows appear in the rowset, if their keys fall within the span of the rowset. If your application does not need to detect the row status SQL_ROW_UPDATED, you should leave the High Cursor Sensitivity checkbox unchecked, as performance is improved. The calculation and comparison of checksums for each row fetched carries an overhead. If this option is enabled, the table oplrvc must have been created beforehand using the appropriate script for the target database. \r\n\r\nEnable logging to the log file \u00E2\u0080\u0094 Check the checkbox and use the associated textbox to provide the full path to a file in which to log diagnostic information.\r\n\r\nClick Next to continue. " . . . . . "Start a JDBC-compliant application e.g, the JDBC Demo Application bundled with the OpenLink JDBC-ODBC Bridge Driver Installer\r\n" . "The fourth dialog enables you to set optional ODBC connection parameters.\n\nRead-only connection \u2014 Specifies whether the connection is \"Read-only.\" Must be unchecked to INSERT, UPDATE, or DELETE records, and to run some Stored Procedures including some built-in functions. \n\nDefer fetching of long data \u2014 Defers fetching of LONG (BINARY, BLOB, etc.) fields in wildcard queries. This provides significant performance increases when fields in query do not include LONG data fields. \n\nDisable interactive login \u2014 Suppresses the ODBC \"Username\" and \"Password\" login dialog boxes when interacting with your ODBC DSN from within an ODBC compliant application.\n \nRow Buffer Size \u2014 This attribute specifies the number of records to be delivered from the driver to the client application in a single batch. Values can range from 1 to 999.\n \nMax Rows Override \u2014 Allows you to set a limit for the maximum number of rows to be returned from a query. The default value of 0 means no limit.\n \nInitial SQL \u2014 Lets you specify a file containing SQL statements that will be run automatically against the database upon connection.\n \nDynamic Cursor Sensitivity \u2014 Enables or disables the row version cache used with dynamic cursors. When dynamic cursor sensitivity is set high, the Cursor Library calculates checksums for each row in the current rowset and compares these with the checksums (if any) already stored in the row version cache for the same rows when fetched previously. If the checksums differ for a row, the row has been updated since it was last fetched and the row status flag is set to SQL_ROW_UPDATED. The row version cache is then updated with the latest checksums for the rowset. From the user's point of view, the only visible difference between the two sensitivity settings is that a row status flag can never be set to SQL_ROW_UPDATED when the cursor sensitivity is low. (The row status is instead displayed as SQL_ROW_SUCCESS.) In all other respects, performance aside, the two settings are the same. Deleted rows don't appear in the rowset. Updates to the row since the row was last fetched are reflected in the row data, and inserted rows appear in the rowset, if their keys fall within the span of the rowset. If your application does not need to detect the row status SQL_ROW_UPDATED, you should leave the High Cursor Sensitivity checkbox unchecked, as performance is improved. The calculation and comparison of checksums for each row fetched carries an overhead. If this option is enabled, the table oplrvc must have been created beforehand using the appropriate script for the target database. \n\nEnable logging to the log file \u2014 Check the checkbox and use the associated textbox to provide the full path to a file in which to log diagnostic information.\n\nClick Next to continue. " . . "Determine that you have a working ODBC Data Source Name that successfully connects to your target database. Also determine the bitness (32-bit or 64-bit) of the driver used as this MUST match the Java Virtual Machine and JDBC-ODBC Bridge Driver bitness." . .