Data Type Storage Demagoda Mind Binary Each character comprises 1 byte of any type of data can be stored in this type of field. Data conversion is not performed (eg, converted into text). How to input to a binary field as an output display, bit1 byte value is YES and NO, and this field can only take one of these two values. Tinyint1 is an integer value between 0 and 255. Money8 bytes between Non-922, 337, 203, 685, 477.5808 and 922, 337, 203, 685, 477.5807. DateTime (see Double) 8 bytes of date or time value between 100 and 9999. UniqueIdentifier128 bits are used for remote procedure calling numbers. REAL4 type single precision floating point value, negative value from - 3.402823E38 to - 1.401298E-45, positive value from 1.401298E-45 to 3.402823E38, and zero. Float8 bytes double precision floating point value, negative value - 1.79769341247E-324, positive value from 4.9465645841247E-324 to 1.79769313486232E308, and zero. Smallint2 bytes of short integers between - 32, 768 and 32, 767. (See "Note") INTEGER4 bytes of long integers between-2,147,483,648 and 2,147,483,647. (See "Note") Decimal17-type precise digital data type, range from 1028 - 1 to - 1028 - 1. Define accuracy (1 - 28) and sizes (0 - definition accuracy). The default accuracy and size are 18 and 0, respectively. TEXT accounts for 2 bytes per character (see "Note") from zero to the maximum 2.14 Jibbytes (GB). Image from zero to a maximum of 2.14 jigrenity as needed. Used for OLE objects. The Character each character accounts for 2 bytes (see "Note") from zero to 255 characters.
Equivalent ANSI SQL Data Type Help> Access 2003> Create and Use Database and Objects> Database Objects> Query> Microsoft Jet SQL Reference> Overview
The following table lists the ANSI SQL data types, their equivalent Microsoft Jet database engine SQL data type and its effective synonyms. The table also lists the equivalent Microsoft® SQL ServerTM data types.
ANSI SQL Data Type Microsoft Jetsql Data Type Synonym Microsoft SQLServer Data Type Bit, Bit VaryingBinary (see "Note") Varbinary, binary varyingbit varyingbinary, varbinary does not support bit (see "Note") Boolean, Logical, Logical1, YesNobit does not support TINYINTINTEGER1, BYTETINYINT does not support COUNTER (see "Note") AUTOINCREMENT (see "Note") does not support MONEYCURRENCYMONEYDATE, TIME, TIMESTAMPDATETIMEDATE, TIME (see "Note") DATETIME do not support UNIQUEIDENTIFIERGUIDUNIQUEIDENTIFIERDECIMALDECIMALNUMERIC, DECDECIMALREALREALSINGLE, FLOAT4, IEEESINGLEREALDOUBLE PRECISION, FLOATFLOATDOUBLE , fLOAT8, IEEEDOUBLE, NUMBER (see "Note") FLOATSMALLINTSMALLINTSHORT, INTEGER2SMALLINTINTEGERINTEGERLONG, INT, INTEGER4INTEGERINTERVAL not supported not supported not supported IMAGELONGBINARY, GENERAL, OLEOBJECTIMAGE does not support TEXT (see "Note") LONGTEXT, LONGCHAR, MEMO, NOTE, NTEXT (See "Note") TextCharacter, National Character VaryingChar (see ") Text (N), AlphaChacter Varying, Nchar, National Character, National Char, National Character, National Char, National Character, National Char, National Character Character Varying, National Char Varying (see "Note") CHAR, VARC Har, Nchar, NVARCHAR Note
The ANSI SQL bit data type does not correspond to the Microsoft Jet SQL bit data type. But it corresponds to the binary data type. There is no ANSI SQL data type equivalent to the Microsoft Jet SQL bit data type. The TimeStamp is no longer supported as a synonym of DateTime. No longer support NUMERIC as a synonym of Float or Double. Now, Numeric can be used as synonyms of Decimal. The longtext field is always stored as a Unicode representation format. If the data type name of the data used is not specified, such as Text (25), a longtext field will be created. This way, the CREATE TABLE statement to be written will generate a consistent data type with Microsoft SQL Server. The char field is always stored as a Unicode representation format, which is equivalent to the ANSI SQL National CHAR data type. If the data type name text of the used text does not specify an optional length, such as TEXT (25), then the data type of the field is equivalent to the CHAR data type. In this way, the rearward compatibility of most Microsoft Jet applications can be maintained, while making the Text Data Type Creter Table Friends ([Friendid) INTEGER, [LastName] text, [firstname] text, [birthdate] Date, [Phone] text, [Notes] MEMO, Constraint [Index1] Primary Key ([FriendId]));