. . . . . . . "ODBC Driver for MySQL Data Source Configuration (Windows)" . . . "

\r\n
1. Open the \"ODBC Data Sources\" Application.
\r\n
2. For 64-bit drivers, configure them with the 64-bit Application. For 32-bit drivers, configure them with the 32-bit Application.
\r\n
3. Select the System DSN tab, then click Add.
\r\n
4. Select the OpenLink \"Lite\" Driver for MySQL Data Sources from the list of available drivers.
\r\n
5. Select the Unicode version of the driver if and only if you are working with multi-byte character sets, as unnecessary translations can significantly affect ODBC performance.
\r\n
6. Click Finish.
\r\n
7. The first dialog prompts for a Data Source Name and optional description.
\r\n
8. Click Next.
\r\n
9. The second dialog prompts for information that identifies the MySQL database server and listen port. It also provides a checkbox that allows you to check your basic connection parameters before setting advanced and optional settings.
\r\n
10. Host - The hostname or IP address of the server on which MySQL runs.
\r\n
11. Port - The TCP port on which MySQL listens.
\r\n
12. Database - The MySQL database.
\r\n
13. Login ID - A MySQL username.
\r\n
14. Connect now to verify that all settings are correct - Will attempt to connect to the database once you click Continue.
\r\n
15. Password - A valid MySQL database password.
\r\n
16. Click Next.
\r\n
17. The third dialog enables you to set MySQL specific parameters.
\r\n
18. No transactions - Disable ODBC transaction management. All transactions will be automatically committed. This prevents palloc() failures with out-of-memory errors when doing really big transactions, such as exporting 10,000 records from Microsoft Access.
\r\n
19. Catalogs return Owner - Check this box so that ODBC API catalog calls return values in catalog columns as the database owner or schema.
\r\n
20. Use Cursor Fetch - This parameter, specific to MySQL 5, enables the use of internal cursors to fetch result sets.
\r\n
21. Prepare Method - Enables you to specify the Prepare/Execute Method. More.
\r\n
22. Character set - Allows you to choose the client character set. (ANSI only).
\r\n
23. Click Next.
\r\n
24. The fourth dialog enables you to set optional ODBC connection parameters:
\r\n
25. Read-only connection - 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
26. Defer fetching of long data - Defers fetching of LONG (BINARY, BLOB, etc.) fields in wildcard queries. This provides significant performance increases when fields in the query do not include LONG data fields.
\r\n
27. Disable interactive login - Suppresses the ODBC \"Username\" and \"Password\" login dialog boxes when interacting with your ODBC DSN from within an ODBC compliant application.
\r\n
28. Row Buffer Size - 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
29. Max Rows Override - 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
30. Initial SQL - Lets you specify a file containing SQL statements that will be run automatically against the database upon connection.
\r\n
31. Dynamic Cursor Sensitivity - 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 carry 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
32. Enable logging to the log file - Check the checkbox and use the associated textbox to provide the full path to a file in which to log diagnostic information.
\r\n
33. Click Next.
\r\n
34. The fifth dialog enables you to set additional parameters to enhance compatibility with applications.
\r\n
35. Enable Microsoft Jet engine options - Facilitates the translation of certain data types for the Microsoft Jet Engine. If you notice that money and other datatypes are mishandled with Microsoft or other applications, test with Jet fix enabled.
\r\n
36. Disable Autocommit - Changes the commit behavior of the OpenLink driver. The default mode is AutoCommit (box unchecked).
\r\n
37. Disable rowset size limit - Disables a limitation enforced by the cursor library. This limitation is enforced by default. It prevents the driver from claiming all available memory when a resultset (typically generated by an accidental query) is very large. The limit is not normally reached.
\r\n
38. Multiple Active Statements Emulation - Enables use of Multiple Active statements in an ODBC application even if the underlying database does not allow this, by emulation within the driver.
\r\n
39. SQL_DBMS Name - Manually overrides the SQLGetInfo(SQL_DBMS_NAME) response returned by the driver. This is required for products like Microsoft InfoPath for which the value should be \"SQL Server\".
\r\n
40. Click Next.
\r\n
41. The final dialog enables you to test your Data Source. Click the Test Data Source button.
\r\n
42. Once a successful connection has been established, click Finish.
\r\n

" . "Data Source Name Configuration Guide" . "

\n
1. Open the \"ODBC Data Sources\" Application.
\n
2. 64-bit drivers should be configured with the 64-bit Application.
\n
3. 32-bit drivers should be configured with the 32-bit Application.
\n
4. Select the System DSN tab, then click Add.
\n
5. Select the OpenLink \"Lite\" Driver for MySQL Data Sources from the list of available drivers. Select the Unicode version of the driver if and only if you are working with multi-byte character sets, as unnecessary translations can significantly affect ODBC performance.
\n
6. Click Finish.
\n
7. The first dialog prompts for a Data Source Name and optional description.
\n
8. Click Next.
\n
9. The second dialog prompts for information that identifies the MySQL database server and listen port. It also provides a checkbox that allows you to check your basic connection parameters before setting advanced and optional settings:
\n
\n
• Host - The hostname or IP address of the server on which MySQL runs
\n
• Port - The TCP port on which MySQL listens
\n
• Database - The MySQL database
\n
• Login ID - A MySQL username
\n
• Connect now to verify that all settings are correct - Will attempt to connect to the database, once you click Continue.
\n
• Password - A valid MySQL database password
\n
\n
10. Click Next.
\n
11. The third dialog enables you to set MySQL specific parameters:
\n
\n
• No transactions - Disable ODBC transaction management. All transactions will be automatically committed. This prevents palloc() failures with out-of-memory errors when doing really big transactions, such as exporting 10,000 records from Microsoft Access.
\n
• Catalogs return Owner - Check this box so that ODBC API catalog calls return values in catalog columns as the database owner or schema.
\n
• Use Cursor Fetch - This parameter, specific to MySQL 5, enables the use of internal cursors to fetch result sets.
\n
• Prepare Method - Enables you to specify the Prepare/Execute Method. More
\n
• Character set - Allows you to choose the client character set. (ANSI only)
\n
\n
12. Click Next.
\n
13. The fourth dialog enables you to set optional ODBC connection parameters:
\n
\n
• Read-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.
\n
• Defer 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.
\n
• Disable 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.
\n
• Row 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.
\n
• Max 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.
\n
• Initial SQL \u00E2\u0080\u0094 Lets you specify a file containing SQL statements that will be run automatically against the database upon connection.
\n
• Dynamic Cursor Sensitivity \u00E2\u0080\u0094 Enables or disables the row version cache used with dynamic cursors.
\n
• Enable 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.
\n
\n
14. Click Next.
\n
15. The fifth dialog enables you to set additional parameters to enhance compatibility with applications:
\n
\n
• Enable Microsoft Jet engine options \u00E2\u0080\u0094 Facilitates translation of certain data types for the Microsoft Jet Engine. If you notice that money and other datatypes are mishandled with Microsoft or other applications, test with Jet fix enabled.
\n
• Disable Autocommit \u00E2\u0080\u0094 Changes the commit behavior of the OpenLink driver. The default mode is AutoCommit (box unchecked).
\n
• Disable rowset size limit \u00E2\u0080\u0094 Disables a limitation enforced by the cursor library. This limitation is enforced by default. It prevents the driver from claiming all available memory when a resultset is very large.
\n
• Multiple Active Statements Emulation \u00E2\u0080\u0094 Enables use of Multiple Active statements in an ODBC application even if the underlying database does not allow this, by emulation within the driver.
\n
• SQL_DBMS Name \u00E2\u0080\u0094 Manually overrides the SQLGetInfo(SQL_DBMS_NAME) response returned by the driver.
\n
\n
16. Click Next.
\n
17. The final dialog enables you to test your Data Source. Click the Test Data Source button.
\n
18. Once a successful connection has been established, click Finish.
\n

\n\n\n\n\n\n" . . . . . "

\r\n
1. Open the \"ODBC Data Sources\" Application.
\r\n
2. 64-bit drivers should be configured with the 64-bit Application.
\r\n
3. 32-bit drivers should be configured with the 32-bit Application.
\r\n
4. Select the System DSN tab, then click Add.
\r\n
5. Select the OpenLink \"Lite\" Driver for MySQL Data Sources from the list of available drivers. Select the Unicode version of the driver if and only if you are working with multi-byte character sets, as unnecessary translations can significantly affect ODBC performance.
\r\n
6. Click Finish.
\r\n
7. The first dialog prompts for a Data Source Name and optional description.
\r\n
8. Click Next.
\r\n
9. The second dialog prompts for information that identifies the MySQL database server and listen port. It also provides a checkbox that allows you to check your basic connection parameters before setting advanced and optional settings:
\r\n
\r\n
• Host - The hostname or IP address of the server on which MySQL runs
\r\n
• Port - The TCP port on which MySQL listens
\r\n
• Database - The MySQL database
\r\n
• Login ID - A MySQL username
\r\n
• Connect now to verify that all settings are correct - Will attempt to connect to the database, once you click Continue.
\r\n
• Password - A valid MySQL database password
\r\n
\r\n
10. Click Next.
\r\n
11. The third dialog enables you to set MySQL specific parameters:
\r\n
\r\n
• No transactions - Disable ODBC transaction management. All transactions will be automatically committed. This prevents palloc() failures with out-of-memory errors when doing really big transactions, such as exporting 10,000 records from Microsoft Access.
\r\n
• Catalogs return Owner - Check this box so that ODBC API catalog calls return values in catalog columns as the database owner or schema.
\r\n
• Use Cursor Fetch - This parameter, specific to MySQL 5, enables the use of internal cursors to fetch result sets.
\r\n
• Prepare Method - Enables you to specify the Prepare/Execute Method. More
\r\n
• Character set - Allows you to choose the client character set. (ANSI only)
\r\n
\r\n
12. Click Next.
\r\n
13. The fourth dialog enables you to set optional ODBC connection parameters:
\r\n
\r\n
• Read-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
• Defer 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
• Disable 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
• Row 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
• Max 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
• Initial SQL \u2014 Lets you specify a file containing SQL statements that will be run automatically against the database upon connection.
\r\n
• Dynamic Cursor Sensitivity \u2014 Enables or disables the row version cache used with dynamic cursors.
\r\n
• Enable 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\n
14. Click Next.
\r\n
15. The fifth dialog enables you to set additional parameters to enhance compatibility with applications:
\r\n
\r\n
• Enable Microsoft Jet engine options \u2014 Facilitates translation of certain data types for the Microsoft Jet Engine. If you notice that money and other datatypes are mishandled with Microsoft or other applications, test with Jet fix enabled.
\r\n
• Disable Autocommit \u2014 Changes the commit behavior of the OpenLink driver. The default mode is AutoCommit (box unchecked).
\r\n
• Disable rowset size limit \u2014 Disables a limitation enforced by the cursor library. This limitation is enforced by default. It prevents the driver from claiming all available memory when a resultset is very large.
\r\n
• Multiple Active Statements Emulation \u2014 Enables use of Multiple Active statements in an ODBC application even if the underlying database does not allow this, by emulation within the driver.
\r\n
• SQL_DBMS Name \u2014 Manually overrides the SQLGetInfo(SQL_DBMS_NAME) response returned by the driver.
\r\n
\r\n
16. Click Next.
\r\n
17. The final dialog enables you to test your Data Source. Click the Test Data Source button.
\r\n
18. Once a successful connection has been established, click Finish.
\r\n

\r\nThe documentation has been formatted with HTML tags according to your guidelines.\r\n\r\n\r\n\r\n\r\n\r\n" . . . . "

\r\n
1. Open the \"ODBC Data Sources\" Application.
\r\n
2. For 64-bit drivers, configure them with the 64-bit Application. For 32-bit drivers, configure them with the 32-bit Application.
\r\n
3. Select the System DSN tab, then click Add.
\r\n
4. Select the OpenLink \"Lite\" Driver for JDBC Data Sources from the list of available drivers.
\r\n
5. Select the Unicode version of the driver if and only if you are working with multi-byte character sets, as unnecessary translations can significantly affect ODBC performance.
\r\n
6. Click Finish.
\r\n
7. The first dialog prompts for a Data Source Name and optional description.
\r\n
8. Click Next.
\r\n
9. The second dialog prompts for information that identifies the MySQL database server and listen port. It also provides a checkbox that allows you to check your basic connection parameters before setting advanced and optional settings.
\r\n
10. Host - The hostname or IP address of the server on which MySQL runs.
\r\n
11. Port - The TCP port on which MySQL listens.
\r\n
12. Database - The MySQL database.
\r\n
13. Login ID - A MySQL username.
\r\n
14. Connect now to verify that all settings are correct - Will attempt to connect to the database once you click Continue.
\r\n
15. Password - A valid MySQL database password.
\r\n
16. Click Next.
\r\n
17. The third dialog enables you to set MySQL specific parameters.
\r\n
18. No transactions - Disable ODBC transaction management. All transactions will be automatically committed. This prevents palloc() failures with out-of-memory errors when doing really big transactions, such as exporting 10,000 records from Microsoft Access.
\r\n
19. Catalogs return Owner - Check this box so that ODBC API catalog calls return values in catalog columns as the database owner or schema.
\r\n
20. Use Cursor Fetch - This parameter, specific to MySQL 5, enables the use of internal cursors to fetch result sets.
\r\n
21. Prepare Method - Enables you to specify the Prepare/Execute Method. More.
\r\n
22. Character set - Allows you to choose the client character set. (ANSI only).
\r\n
23. Click Next.
\r\n
24. The fourth dialog enables you to set optional ODBC connection parameters:
\r\n
25. Read-only connection - 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
26. Defer fetching of long data - Defers fetching of LONG (BINARY, BLOB, etc.) fields in wildcard queries. This provides significant performance increases when fields in the query do not include LONG data fields.
\r\n
27. Disable interactive login - Suppresses the ODBC \"Username\" and \"Password\" login dialog boxes when interacting with your ODBC DSN from within an ODBC compliant application.
\r\n
28. Row Buffer Size - 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
29. Max Rows Override - 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
30. Initial SQL - Lets you specify a file containing SQL statements that will be run automatically against the database upon connection.
\r\n
31. Dynamic Cursor Sensitivity - 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 carry 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
32. Enable logging to the log file - Check the checkbox and use the associated textbox to provide the full path to a file in which to log diagnostic information.
\r\n
33. Click Next.
\r\n
34. The fifth dialog enables you to set additional parameters to enhance compatibility with applications.
\r\n
35. Enable Microsoft Jet engine options - Facilitates the translation of certain data types for the Microsoft Jet Engine. If you notice that money and other datatypes are mishandled with Microsoft or other applications, test with Jet fix enabled.
\r\n
36. Disable Autocommit - Changes the commit behavior of the OpenLink driver. The default mode is AutoCommit (box unchecked).
\r\n
37. Disable rowset size limit - Disables a limitation enforced by the cursor library. This limitation is enforced by default. It prevents the driver from claiming all available memory when a resultset (typically generated by an accidental query) is very large. The limit is not normally reached.
\r\n
38. Multiple Active Statements Emulation - Enables use of Multiple Active statements in an ODBC application even if the underlying database does not allow this, by emulation within the driver.
\r\n
39. SQL_DBMS Name - Manually overrides the SQLGetInfo(SQL_DBMS_NAME) response returned by the driver. This is required for products like Microsoft InfoPath for which the value should be \"SQL Server\".
\r\n
40. Click Next.
\r\n
41. The final dialog enables you to test your Data Source. Click the Test Data Source button.
\r\n
42. Once a successful connection has been established, click Finish.
\r\n

" . . "ODBC Driver for MySQL Data Source Configuration (Windows)" . . . "Lite Edition (Single-Tier) ODBC Driver for MySQL Data Source Configuration (Windows)" . . . . . . . "Lite Edition (Single-Tier) ODBC Driver for MySQL Data Source Configuration (Windows)" . . . . "

\n
1. Open the \"ODBC Data Sources\" Application.
\n
2. 64-bit drivers should be configured with the 64-bit Application.
\n
3. 32-bit drivers should be configured with the 32-bit Application.
\n
4. Select the System DSN tab, then click Add.
\n
5. Select the OpenLink \"Lite\" Driver for MySQL Data Sources from the list of available drivers. Select the Unicode version of the driver if and only if you are working with multi-byte character sets, as unnecessary translations can significantly affect ODBC performance.
\n
6. Click Finish.
\n
7. The first dialog prompts for a Data Source Name and optional description.
\n
8. Click Next.
\n
9. The second dialog prompts for information that identifies the MySQL database server and listen port. It also provides a checkbox that allows you to check your basic connection parameters before setting advanced and optional settings:
\n
\n
• Host - The hostname or IP address of the server on which MySQL runs
\n
• Port - The TCP port on which MySQL listens
\n
• Database - The MySQL database
\n
• Login ID - A MySQL username
\n
• Connect now to verify that all settings are correct - Will attempt to connect to the database, once you click Continue.
\n
• Password - A valid MySQL database password
\n
\n
10. Click Next.
\n
11. The third dialog enables you to set MySQL specific parameters:
\n
\n
• No transactions - Disable ODBC transaction management. All transactions will be automatically committed. This prevents palloc() failures with out-of-memory errors when doing really big transactions, such as exporting 10,000 records from Microsoft Access.
\n
• Catalogs return Owner - Check this box so that ODBC API catalog calls return values in catalog columns as the database owner or schema.
\n
• Use Cursor Fetch - This parameter, specific to MySQL 5, enables the use of internal cursors to fetch result sets.
\n
• Prepare Method - Enables you to specify the Prepare/Execute Method. More
\n
• Character set - Allows you to choose the client character set. (ANSI only)
\n
\n
12. Click Next.
\n
13. The fourth dialog enables you to set optional ODBC connection parameters:
\n
\n
• Read-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
• Defer 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
• Disable 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
• Row 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
• Max 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
• Initial SQL \u2014 Lets you specify a file containing SQL statements that will be run automatically against the database upon connection.
\n
• Dynamic Cursor Sensitivity \u2014 Enables or disables the row version cache used with dynamic cursors.
\n
• Enable 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
\n
14. Click Next.
\n
15. The fifth dialog enables you to set additional parameters to enhance compatibility with applications:
\n
\n
• Enable Microsoft Jet engine options \u2014 Facilitates translation of certain data types for the Microsoft Jet Engine. If you notice that money and other datatypes are mishandled with Microsoft or other applications, test with Jet fix enabled.
\n
• Disable Autocommit \u2014 Changes the commit behavior of the OpenLink driver. The default mode is AutoCommit (box unchecked).
\n
• Disable rowset size limit \u2014 Disables a limitation enforced by the cursor library. This limitation is enforced by default. It prevents the driver from claiming all available memory when a resultset is very large.
\n
• Multiple Active Statements Emulation \u2014 Enables use of Multiple Active statements in an ODBC application even if the underlying database does not allow this, by emulation within the driver.
\n
• SQL_DBMS Name \u2014 Manually overrides the SQLGetInfo(SQL_DBMS_NAME) response returned by the driver.
\n
\n
16. Click Next.
\n
17. The final dialog enables you to test your Data Source. Click the Test Data Source button.
\n
18. Once a successful connection has been established, click Finish.
\n

\nThe documentation has been formatted with HTML tags according to your guidelines.\n\n\n\n\n\n" . . "

\r\n
1. Open the \"ODBC Data Sources\" Application.
\r\n
2. 64-bit drivers should be configured with the 64-bit Application.
\r\n
3. 32-bit drivers should be configured with the 32-bit Application.
\r\n
4. Select the System DSN tab, then click Add.
\r\n
5. Select the OpenLink \"Lite\" Driver for MySQL Data Sources from the list of available drivers. Select the Unicode version of the driver if and only if you are working with multi-byte character sets, as unnecessary translations can significantly affect ODBC performance.
\r\n
6. Click Finish.
\r\n
7. The first dialog prompts for a Data Source Name and optional description.
\r\n
8. Click Next.
\r\n
9. The second dialog prompts for information that identifies the MySQL database server and listen port. It also provides a checkbox that allows you to check your basic connection parameters before setting advanced and optional settings:
\r\n
\r\n
• Host - The hostname or IP address of the server on which MySQL runs
\r\n
• Port - The TCP port on which MySQL listens
\r\n
• Database - The MySQL database
\r\n
• Login ID - A MySQL username
\r\n
• Connect now to verify that all settings are correct - Will attempt to connect to the database, once you click Continue.
\r\n
• Password - A valid MySQL database password
\r\n
\r\n
10. Click Next.
\r\n
11. The third dialog enables you to set MySQL specific parameters:
\r\n
\r\n
• No transactions - Disable ODBC transaction management. All transactions will be automatically committed. This prevents palloc() failures with out-of-memory errors when doing really big transactions, such as exporting 10,000 records from Microsoft Access.
\r\n
• Catalogs return Owner - Check this box so that ODBC API catalog calls return values in catalog columns as the database owner or schema.
\r\n
• Use Cursor Fetch - This parameter, specific to MySQL 5, enables the use of internal cursors to fetch result sets.
\r\n
• Prepare Method - Enables you to specify the Prepare/Execute Method. More
\r\n
• Character set - Allows you to choose the client character set. (ANSI only)
\r\n
\r\n
12. Click Next.
\r\n
13. The fourth dialog enables you to set optional ODBC connection parameters:
\r\n
\r\n
• Read-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
• Defer 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
• Disable 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
• Row 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
• Max 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
• Initial SQL \u00E2\u0080\u0094 Lets you specify a file containing SQL statements that will be run automatically against the database upon connection.
\r\n
• Dynamic Cursor Sensitivity \u00E2\u0080\u0094 Enables or disables the row version cache used with dynamic cursors.
\r\n
• Enable 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\n
14. Click Next.
\r\n
15. The fifth dialog enables you to set additional parameters to enhance compatibility with applications:
\r\n
\r\n
• Enable Microsoft Jet engine options \u00E2\u0080\u0094 Facilitates translation of certain data types for the Microsoft Jet Engine. If you notice that money and other datatypes are mishandled with Microsoft or other applications, test with Jet fix enabled.
\r\n
• Disable Autocommit \u00E2\u0080\u0094 Changes the commit behavior of the OpenLink driver. The default mode is AutoCommit (box unchecked).
\r\n
• Disable rowset size limit \u00E2\u0080\u0094 Disables a limitation enforced by the cursor library. This limitation is enforced by default. It prevents the driver from claiming all available memory when a resultset is very large.
\r\n
• Multiple Active Statements Emulation \u00E2\u0080\u0094 Enables use of Multiple Active statements in an ODBC application even if the underlying database does not allow this, by emulation within the driver.
\r\n
• SQL_DBMS Name \u00E2\u0080\u0094 Manually overrides the SQLGetInfo(SQL_DBMS_NAME) response returned by the driver.
\r\n
\r\n
16. Click Next.
\r\n
17. The final dialog enables you to test your Data Source. Click the Test Data Source button.
\r\n
18. Once a successful connection has been established, click Finish.
\r\n

\r\n\r\n\r\n\r\n\r\n\r\n" .