SQL Data Type & filePro Edits

The ODBC database data type is translated to a filePro edit type when using the High-Level method. The following chart identifies the filePro edit type that is applied for the corresponding ODBC data types.

SQL data type | Default filePro data type | Notes
GUID (-11) | * |
WLONGVARCHAR (-10) | * |
WVARCHAR (-9) | * |
WCHAR (-8) | * |
BIT (-7) | .0 |
TINYINT (-6) | .0 |
BIGINT (-5) | * |
LONGVARBINARY (-4) | * |
VARBINARY (-3) | * |
BINARY (-2) | * |
LONGVARCHAR (-1) | * |
UNKNOWN_TYPE (0) | * |
CHAR (1) | * |
NUMERIC (2) | .n | "n" is determined by the "scale" setting of the field.
DECIMAL (3) | .n | "n" is determined by the "scale" setting of the field.
INTEGER (4) | .0 |
SMALLINT (5) | .0 |
FLOAT (6) | F |
REAL (7) | F |
DOUBLE (8) | F |
DATE (9) | MDYY/ |
TIME (10) | HMS |
TIMESTAMP (11) | * | You can change the filePro type to a date field, and filePro will use just the date portion of the field. Or, you can use a time field, and filePro will use just the time portion.
VARCHAR (12) | * |

Notes The default length of the field (except for MDYY/ and HMS) is determined by the "precision" setting of the SQL field, except for NUMERIC and DECIMAL, which use "precision + 2" for the length. The above SQL data types are the internal representation format used by the SQL data engine. ODBC data sources may have different names for the field types, but they are all represented internally by one of the above types. For example, SQL Server calls its auto-increment field type "int identity", and stores it as INTEGER. Microsoft Access also uses INTEGER, but calls it "COUNTER". Microsoft Access "currency" data type is stored as a NUMERIC type, precision 19, scale 4. However, there appears to be some problem with currency fields that prevents filePro from saving a record that has a currency-type field in it.