Oracle 5.0 Reference Manual page 1831

• If you are using Access 2000, get and install the newest (version 2.6 or higher) Microsoft MDAC
(Microsoft Data Access
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
support.microsoft.com/default.aspx?scid=kb;EN-US;q239114. This fixes some cases where columns
are marked as
• For all versions of Access, enable the Connector/ODBC
Access 2.0, also enable the
• Include a
• Include a
• Use only
DOUBLE
usually is that new or updated rows may show up as
rows.
• If you are using Connector/ODBC to link to a table that has a
displayed as #DELETED. The work around solution is:
• Have one more dummy column with
• Select the
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
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
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
This error occurs only with MySQL tables using the
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
You can get the patch that addresses this problem from
scid=kb;EN-US;q319243.
Connector/ODBC Notes and Tips
Components) from http://support.microsoft.com/kb/110093. This fixes
in Access.
#DELETED#
Simulate ODBC 1.0
in all tables that you want to be able to update.
TIMESTAMP
primary key in the table. If not, new or updated rows may show up as #DELETED#.
float fields. Access fails when comparing with single-precision floats. The symptom
Change BIGINT columns to INT
exception.
Return matching rows
option.
#DELETED#
BIGINT
as the data type.
TIMESTAMP
option in the connection dialog in ODBC DSN
Return Matching Rows
Syntax Error.
Syntax
or
TEXT VARCHAR
http://support.microsoft.com/default.aspx?
1811
option. For
or that you cannot find or update
column, the results are
option in the DSN configuration
Error.
data types. You can fix this error
http://