Oracle 5.0 Reference Manual page 1830

Select the
Return matching rows
20.1.7.3. Connector/ODBC Errors and Resolutions (FAQ)
The following section details some common errors and their suggested fix or alternative solution.
If you are still experiencing problems, use the Connector/ODBC mailing list; see
"Connector/ODBC Community
Many problems can be resolved by upgrading your Connector/ODBC drivers to the latest available
release. On Windows, make sure that you have the latest versions of the Microsoft Data Access
Components (MDAC) installed.
64-Bit Windows and ODBC Data Source Administrator
I have installed Connector/ODBC on Windows XP x64 Edition or Windows Server 2003 R2 x64. The
installation completed successfully, but the Connector/ODBC driver does not appear in
Source Administrator.
This is not a bug, but is related to the way Windows x64 editions operate with the ODBC driver. On
Windows x64 editions, the Connector/ODBC driver is installed in the
folder. However, the default
the
Administrative Tools
%SystemRoot%\system32
On Windows x64 editions, use the ODBC administration tool located at
\SysWOW64\odbcad32.exe, this will correctly locate the installed Connector/ODBC drivers and
enable you to create a Connector/ODBC DSN.
This issue was originally reported as Bug #20301.
Error 10061 (Cannot connect to server)
When connecting or using the Test button in
(Cannot connect to server)
This error can be raised by a number of different issues, including server problems, network problems,
and firewall and port blocking problems. For more information, see
to [local] MySQL
"Transactions are not enabled" Error
The following error is reported when using transactions:
This error indicates that you are trying to use
transactions. Transactions are supported within MySQL when using the
which is the default storage engine in MySQL 5.5 and higher. In versions of MySQL before MySQL 5.1,
you may also use the
Check the following before continuing:
• Verify that your MySQL server supports a transactional database engine. Use
obtain a list of the available engine types.
• Verify that the tables you are updating use a transactional database engine.
• Ensure that you have not enabled the
#DELETED# Records Reported by Access
Access reports records as
If the inserted or updated records are shown as
Connector/ODBC Notes and Tips
option.
Support".
ODBC Data Source Administrator
or
Control Panel
folder, and only searches this folder for ODBC drivers.
server".
engine.
BDB
disable transactions
when inserting or updating records in linked tables.
#DELETED#
1810
in Windows x64 Editions is located in the
ODBC Data Source Administrator
Section C.5.2.2,
Transactions are not enabled
transactions with a MySQL table that does not support
in Access, then:
#DELETED#
Section 20.1.8.1,
ODBC Data
%SystemRoot%\SysWOW64
that is available through
%SystemRoot%
I get error 10061
"Can't connect
database engine,
InnoDB
SHOW ENGINES
option in your DSN.
to