MS Access to MySQL

Char/VarChar Binary If a column marked BINARY is used in an expression, the whole expression is compared as a BINARY value, resulting in case-sensitive comparison You may use "LIKE BINARY" statement or stored procedure to implement case-sensitive comparison with Char/VarChar data without BINARY property.
Set Not supported in MS Access. An exception will be raised while copying table structures. You may alter the SQL datable to change the data type to Char type.
Enum Not supported in MS Access. An exception will be raised. You may alter the SQL table to change the data type to Char type.
IntegerType Unsigned Not supported in MS Access. These integer fields will be converted without the "unsigned" property, so it is better to have your application not to use unsigned data type, and handle "unsigned" constraints in the program. The only unsigned data type in MS Access is "Byte".
BigInt Not supported in MS Access. An BigInt like 9223372036854775807 will be converted to Double (8-byte) type and value will become 9.22337203685478E+18. If you really need BigInt data, you might not want to export / port the database to MS Access that does not support 8-byte integer.
TimeStamp After setting the default value of a DateTime field of MS Access as function "now()", the value in a row will be the time of inserting. However, when you modify the row later, the value will remain the same. There is no way for the JET Engine to support TimeStamp. So you may have to write codes to simulate TimeStamp effects.
Decimal The decimal type in Ms Access is not exactly equivalent with the decimal type in MySQL.