![background image](http://html1.mh-extra.com/html/oracle/5-0/5-0_reference-manual_16461961831.webp)
Connector/ODBC Notes and Tips
1811
• If you are using Access 2000, get and install the newest (version 2.6 or higher) Microsoft MDAC
(
Microsoft Data Access Components
) from
http://support.microsoft.com/kb/110093
. This fixes
a bug in Access that when you export data to MySQL, the table and column names aren't specified.
Also, get and apply the Microsoft Jet 4.0 Service Pack 5 (SP5), which can be found at
http://
support.microsoft.com/default.aspx?scid=kb;EN-US;q239114
. This fixes some cases where columns
are marked as
#DELETED#
in Access.
• For all versions of Access, enable the Connector/ODBC
Return matching rows
option. For
Access 2.0, also enable the
Simulate ODBC 1.0
option.
• Include a
TIMESTAMP
in all tables that you want to be able to update.
• Include a
primary key
in the table. If not, new or updated rows may show up as
#DELETED#
.
• Use only
DOUBLE
float fields. Access fails when comparing with single-precision floats. The symptom
usually is that new or updated rows may show up as
#DELETED#
or that you cannot find or update
rows.
• If you are using Connector/ODBC to link to a table that has a
BIGINT
column, the results are
displayed as
#DELETED
. The work around solution is:
• Have one more dummy column with
TIMESTAMP
as the data type.
• Select the
Change BIGINT columns to INT
option in the connection dialog in ODBC DSN
Administrator.
• Delete the table link from Access and re-create it.
Old records still display as
#DELETED#
, but newly added/updated records are displayed properly.
Write Conflicts or Row Location Errors
How do I handle Write Conflicts or Row Location errors?
If you see the following errors, select the
Return Matching Rows
option in the DSN configuration
dialog, or specify
OPTION=2
, as the connection parameter:
Write Conflict. Another user has changed your data.
Row cannot be located for updating. Some values may have been changed
since it was last read.
Importing from Access 97
Exporting data from Access 97 to MySQL reports a
Syntax Error
.
This error is specific to Access 97 and versions of Connector/ODBC earlier than 3.51.02. Update to the
latest version of the Connector/ODBC driver to resolve this problem.
Importing from Microsoft DTS
Exporting data from Microsoft DTS to MySQL reports a
Syntax Error
.
This error occurs only with MySQL tables using the
TEXT
or
VARCHAR
data types. You can fix this error
by upgrading your Connector/ODBC driver to version 3.51.02 or higher.
SQL_NO_DATA Exception from ODBC.NET
Using ODBC.NET with Connector/ODBC, while fetching empty string (0 length), it starts giving the
SQL_NO_DATA
exception.
You can get the patch that addresses this problem from
http://support.microsoft.com/default.aspx?
scid=kb;EN-US;q319243
.
Содержание 5.0
Страница 1: ...MySQL 5 0 Reference Manual ...
Страница 18: ...xviii ...
Страница 60: ...40 ...
Страница 396: ...376 ...
Страница 578: ...558 ...
Страница 636: ...616 ...
Страница 844: ...824 ...
Страница 1234: ...1214 ...
Страница 1426: ...MySQL Proxy Scripting 1406 The following diagram shows an overview of the classes exposed by MySQL Proxy ...
Страница 1427: ...MySQL Proxy Scripting 1407 ...
Страница 1734: ...1714 ...
Страница 1752: ...1732 ...
Страница 1783: ...Configuring Connector ODBC 1763 ...
Страница 1793: ...Connector ODBC Examples 1773 ...
Страница 1839: ...Connector Net Installation 1819 2 You must choose the type of installation to perform ...
Страница 1842: ...Connector Net Installation 1822 5 Once the installation has been completed click Finish to exit the installer ...
Страница 1864: ...Connector Net Visual Studio Integration 1844 Figure 20 24 Debug Stepping Figure 20 25 Function Stepping 1 of 2 ...
Страница 2850: ...2830 ...
Страница 2854: ...2834 ...
Страница 2928: ...2908 ...
Страница 3000: ...2980 ...
Страница 3122: ...3102 ...
Страница 3126: ...3106 ...
Страница 3174: ...3154 ...
Страница 3232: ...3212 ...