Saya kutipkan langsung sesuai aslinya untuk menjadi dokumentasi di sini.
To improve the integration between Microsoft Access and MySQL through Connector/ODBC:
-
For all versions of Access, enable the Connector/ODBC
Return matching rows
option. For Access 2.0, also enable theSimulate ODBC 1.0
option. -
Include a
TIMESTAMP
column in all tables that you want to be able to update. For maximum portability, do not use a length specification in the column declaration (which is unsupported within MySQL in versions earlier than 4.1). -
Include a primary
key in each MySQL table you want to use with
Access. 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.
#DELETED#
, but newly added/updated records are displayed properly. -
Have one more dummy column with
-
If you still get the error
Another user has changed your data
after adding aTIMESTAMP
column, the following trick may help you:
Do not use atable
data sheet view. Instead, create a form with the fields you want, and use thatform
data sheet view. Set theDefaultValue
property for theTIMESTAMP
column toNOW()
. Consider hiding theTIMESTAMP
column from view so your users are not confused. -
In some cases, Access may generate SQL statements that
MySQL cannot understand. You can fix this by selecting
"Query|SQLSpecific|Pass-Through"
from the Access menu. -
On Windows NT, Access reports
BLOB
columns asOLE OBJECTS
. If you want to haveMEMO
columns instead, changeBLOB
columns toTEXT
withALTER TABLE
. -
Access cannot always handle the MySQL
DATE
column properly. If you have a problem with these, change the columns toDATETIME
. -
If you have in Access a column defined as
BYTE
, Access tries to export this asTINYINT
instead ofTINYINT UNSIGNED
. This gives you problems if you have values larger than 127 in the column. -
If you have very large (long) tables in Access, it might
take a very long time to open them. Or you might run low
on virtual memory and eventually get an
ODBC Query Failed
error and the table cannot open. To deal with this, select the following options:
- Return Matching Rows (2)
- Allow BIG Results (8).
OPTION=10
).
- Read How to Trap ODBC Login Error Messages in Access
-
Optimizing Access ODBC Applications
- For a list of tools that can be used with Access and ODBC data sources, refer to http://www.mysql.com/portal/software/convertors/.
Tidak ada komentar:
Posting Komentar