|
Import Code |
CONNX Data Type |
SQL Data Type |
SQL Length |
VMS Equivalent Data Types |
Description |
|
357 |
TNRD Julian Date |
Date |
6 |
|
Customer-specific Julian data offset from 1/1/1975 |
|
358 |
TNRD Rev Julian Date |
Date |
6 |
|
Customer-specific reverse Julian data offset from 1/1/1975 |
|
359 |
TNRD Identification number |
Varchar |
-1 |
|
Customer-specific suffix delimited ID number |
|
360 |
TNRD Surname |
Varchar |
-1 |
|
Customer-specific suffix delimited Surname |
|
361 |
TNRD First Name and Initial |
Varchar |
-1 |
|
Customer-specific suffix delimited First name and initial |
|
362 |
TNRD Care of |
Varchar |
-1 |
|
Customer-specific suffix delimited Care of |
|
363 |
TNRD Street Address Number |
Varchar |
-1 |
|
Customer-specific suffix delimited Street Address Number |
|
364 |
TNRD Street Address Name |
Varchar |
-1 |
|
Customer-specific suffix delimited Street Address Name |
|
365 |
TNRD St Address City/Province |
Varchar |
-1 |
|
Customer-specific suffix delimited Street Address City and Province |
|
366 |
TNRD St Address Postal Code |
Varchar |
-1 |
|
Customer-specific suffix delimited Street Address Postal Code |
|
367 |
TNRD Home Phone |
Varchar |
-1 |
|
Customer-specific suffix delimited Home Phone |
|
368 |
TNRD Work Phone |
Varchar |
-1 |
|
Customer-specific suffix delimited Work Phone |
|
369 |
TNRD Alt Address Num & Street |
Varchar |
-1 |
|
Customer-specific suffix delimited Alternate Street Address Number and Name |
|
370 |
TNRD Alt Address City & Prov |
Varchar |
-1 |
|
Customer-specific suffix delimited Alternate Address City and Province |
|
371 |
TNRD Alt Address Postal Code |
Varchar |
-1 |
|
Customer-specific suffix delimited Alternate Address Postal Code |
|
372 |
TNRD School |
Varchar |
-1 |
|
Customer-specific suffix delimited School |
|
373 |
TNRD Parent or Guardian |
Varchar |
-1 |
|
Customer-specific suffix delimited Parent or Guardian |
|
374 |
TNRD Previous Barcode |
Varchar |
-1 |
|
Customer-specific suffix delimited Previous Barcode |
|
375 |
TNRD Next Barcode |
Varchar |
-1 |
|
Customer-specific suffix delimited Next Barcode |
|
376 |
TNRD Xref See |
Long |
4 |
|
Customer-specific prefix delimited See |
|
377 |
TNRD Xref See Also |
Long |
4 |
|
Customer-specific prefix delimited See Also |
|
378 |
TNRD Xref See From |
Long |
4 |
|
Customer-specific prefix delimited See From |
|
379 |
TNRD Xref See Also From |
Long |
4 |
|
Customer-specific prefix delimited See Also From |
|
380 |
TNRD Notes |
Varchar |
-1 |
|
Customer-specific prefix delimited Notes |
|
381 |
Marc BIB Decimal |
Decimal |
21 |
|
Customer-specific base 240 number conversion |
|
382 |
Marc BIB Tag |
Long |
4 |
|
Customer-specific base 240 number conversion |
|
383 |
Adonix Date |
Date |
6 |
|
Customer-specific Julian date offset from 12/31/1599 |
|
384 |
Text Left Space Pad -> FmtDbl |
DOUBLE |
8 |
|
|
|
385 |
Numeric Data (YYMMDD) |
Date |
6 |
|
Three- byte date field where the date is taken from the decimal digits of the values. Thus a numeric value of 750824 is interpreted as August 24 1975. Note that the year field uses a century window where values < 25 are assigned century 2000, everything else 1900. The new function is far more customer specific: TPADateOfBirth(date, centuryCode) Inputs: date - base birth date, for example a field of Numeric Date type. centuryCode - integer value indicating century of birth, 8 = 1800, 9 = 1900, 0 == 2000, no other valid values. |
|
386 |
VISTA Date (Julian 12/31/1919) |
Date |
6 |
|
Julian Date offset from 12/31/1919. |
|
387 |
DBMS Key |
CHAR |
22 |
|
|
|
388 |
Encapsulated Date (cyMMDD) |
DATE |
6 |
|
Byte 0 -> binary number representing the most significant two digits of a four digit year. Byte 1 -> binary number representing the least significant two digits of a four digit year. Thus, if given the first two bytes values of 20, 03, the year for this date are 2003. Bytes 2 & 3 are the numeric characters representing the month of the year. Bytes 4 & 5 are the numeric characters representing the day of the month. Thus a value of 0x010131313131 is a date of November (month 11) 11 (day 11) in the year 101. |
|
389 |
Rev Encapsulated Date (MMDDcy) |
DATE |
6 |
|
Byte 0 -> binary number representing the most significant two digits of a four digit year. Byte 1 -> binary number representing the least significant two digits of a four digit year. Thus, if given the first two bytes values of 20, 03, the year for this date are 2003. Bytes 2 & 3 are the numeric characters representing the month of the year. Bytes 4 & 5 are the numeric characters representing the day of the month. Thus a value of 0x010131313131 is a date of November (month 11) 11 (day 11) in the year 101. |
|
390 |
Text (Right Space Padded) |
CHAR |
-1 |
|
|
|
391 |
Text (Expandable) |
VARCHAR |
-1 |
|
|
|
392 |
Text Date (YYYYMM) |
DATE |
6 |
|
For YYYYMM , if YYYYMM was 200203, the SQL date would be March 1, 2003. The day of the month is always one (1).
|
|
393 |
Text Date 2000 (YYMM) |
DATE |
6 |
|
For YYMM , if YYMM was 0304, the SQL date would be April 1, 2003. The day of the month is always one (1).
For YYMM , if YYMM was 2304, the SQL date would be April 1, 1923. The day of the month is always one (1).
The break Year = 20 (For years below 20, add 2000; for years above 20, add 1900. The break year is configurable.) |
|
394 |
Text Date (MMYYYY) |
DATE |
6 |
|
For MMYYYY , if MMYYYY was 032002, the SQL date would be March 1, 2003. The day of the month is always one (1). |
|
395 |
Text Date 2000 (MMYY) |
DATE |
6 |
|
For MMYY , if MMYY was 0403, the SQL date would be April 1, 2003. The day of the month is always one (1). For MMYY , if MMYY was 0423, the SQL date would be April 1, 1923. The day of the month is always one (1).
The break Year = 20 (For years below 20, add 2000; for years above 20, add 1900. The break year is configurable.) |
|
396 |
Text Date (YYYY) |
DATE |
6 |
|
For YYYY, if YYYY was 2004, the SQL Date would be January 1, 2004. The day of the month is always one (1). The month is always January. |
|
397 |
Text Date 2000 (YY) |
DATE |
6 |
|
for YY, if YY was 04, the SQL Date would be January 1, 2004. The day of the month is always one. The month is always January. For YY, if YY was 34, the SQL Date would be January 1, 1934. The day of the month is always one (1). The month is always January.
The break Year = 20 (For years below 20, add 2000; for years above 20, add 1900. The break year is configurable.) |
|
398 |
Text Date (MM) |
DATE |
6 |
|
For MM, if MM was 11, the SQL Date would be November 1, 2003. The year returned is the current year. The day of the month is always one (1). |
|
399 |
Text Date (DD) |
DATE |
6 |
|
For DD, if DD = 30, the SQL Date would be January 30, 2003. The year returned is the current year. The month is always January. |
|
400 |
Fairfield Text Date (MMDD) |
DATE |
6 |
|
For MMDD, if MM were 11 and DD were 20, then the SQL Date would be November 20, 1900. The year returned is always 1900. |
|
401 |
Fairfield Text Date (MM) |
DATE |
6 |
|
For MMDD, if MM were 11 and DD were 20, then the SQL Date would be November 20, 1900. The year returned is always 1900. |
|
402 |
Fairfield Text Date (DD) |
DATE |
6 |
|
For DD, if DD were 20, then the SQL Date would be January 20, 1900. The year returned in always 1900. The month returned is always January. |
|
403 |
Adabas Natural Date |
DATE |
6 |
|
|
|
404 |
Adabas Natural Time |
TIME |
6 |
|
|
|
405 |
VMS Double -> Currency |
Currency |
21 |
|
|
|
406 |
PostgreSQL Numeric -> Decimal |
DECIMAL |
-15 |
|
|