This value rounds up to the integer 0, and since the zero day maps to, this is the date used.Ī pipe character (|) cannot be used in a date value, even if enclosed in back quotes.ĭata type limited to Microsoft Access 4.0. Otherwise, Microsoft Access will treat the value as an arithmetic expression and will not raise a warning or error.įor example, the date "March 5, 1996" must be represented as or # otherwise, if only is submitted, Microsoft Access will evaluate this as 3 divided by 5 divided by 1996. Procedures should be used to pass character data when using any special character in a character data type column.ĭate values must be either delimited according to the ODBC canonical date format or delimited by the datetime delimiter ("#"). Use two consecutive single quotation marks ('') to represent one single quotation mark ('). Data typeĬreating a BINARY, VARBINARY, or VARCHAR column of zero or unspecified length actually returns a 510-byte column.Įven though a Microsoft Access NUMBER field with a FieldSize equal to BYTE is unsigned, a negative number can be inserted into the field when using the Microsoft Access driver.Ī character string literal can contain any ANSI character (1-255 decimal). The following table shows limitations on Microsoft Access data types.
All conversions in Appendix D of the ODBC Programmer's Reference are supported for the SQL data types listed in the previous table. You can and should define a width, but Access doesn't use fixed width storage so is not as wasteful of disk space. Essentially the same as the Character type in xBase. It will not return all Microsoft Access data types if more than one Microsoft Access type is mapped to the same ODBC SQL data type. Field types in Access are somewhat different to those in xBase. Unicode and Access 4.0 applications only. The following table shows the Microsoft Access data types, data types used to create tables, and ODBC SQL data types.