Range: True or False
The parameter correct_bad_days specifies whether the DATABridge Client should treat a DMSII date with a bad day value as an error or attempt to correct it by setting the value to last day for the given month and year.
This parameter does not apply in the following circumstances:
- Dates whose day values are greater than 31
- DMSII Julian dates (dms_subtype values 17, 18, 27, 28, 37, 38)
- MISER dates—DMSII dates that use a count of days since
12/31/1899 (dms_subtype value 1)
- LINC dates—DMSII dates that use a count of days since
1/1/baseyear (dms_subtype value 3)
Set this parameter as follows:
- Set correct_bad_days to True if you want the DATABridge Client to set bad DMSII dates to the last day for the given month. In this case, a bad date would be February 29, 2002 because 2002 is not a leap year. The DATABridge Client would correct this date to February 28, 2002. Likewise, a date of September 31 would be corrected to September 30, regardless of the year because September always has 30 days.
- Set correct_bad_days to False if you want the DATABridge Client to store bad dates as NULL. If the DAOPT_Nulls_Allowed bit in the da_options column of the corresponding DATAITEMS entry is not set, the bad date is stored as 1/1/1900 in SQL Server.