| - | ||||||||||||||
| none | ||||||||||||||
| Windows 3.0 or later | ||||||||||||||
| Operating System Clock | ||||||||||||||
| 14 Aug 1999 | ||||||||||||||
|
Operational Range for Data: Generally January 1, 1948 – December 31, 2075, butJanuary 1, 1993 – December 31, 2075 for certain online banking services. How the product handles dates: Money version 1.0 accepts from 1/1/1948 through 12/31/2075. It uses a field oriented date structure with 16 bits to represent dates:
These date values are zero-based, which means to represent all possible days in a month, 31 days, and starting with 0, you need 0-30. 5 bits are needed to represent 0-30 days. To represent all possible months in a year, 12 months, and starting with 0, you need 0-11. 4 bits are needed to represent 0-11 months. This means there are 7 bits left out of the 16-bit structure for years. 7 bits can represent a maximum of 127 years. Therefore, starting in 1948, the maximum range is 1948 + 127 = 2075.
Money version 1.0 handles 4-digits dates in the following manner:
Microsoft Money supports the QIF data transfer protocol developed by Intuit. Most versions of QIF have represented dates using a 2-digit year format. While the data stored in Money is Year 2000 compliant, Money needs to use a heuristic to determine the best 2-digit date to use when importing to or exporting from the QIF format. In some versions, QIF uses an apostrophe to denote dates in the 2000s. For example: 1/31’01 indicates January 31, 2001. Presented below is a table describing how Money interprets QIF data ranges:
| ||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
| - | ||||||||||||||
| none | ||||||||||||||
| Windows 3.0 or later | ||||||||||||||
| Operating system clock | ||||||||||||||
| 14 Aug 1999 | ||||||||||||||
|
Operational Range for Data: Generally January 1, 1948 – December 31, 2075, butJanuary 1, 1993 – December 31, 2075 for certain online banking services How the product handles dates: Money version 2.0 accepts dates from 1/1/1948 through 12/31/2075. It uses a field oriented date structure with 16 bits to represent dates:
These date values are zero-based, which means to represent all possible days in a month, 31 days, and starting with 0, you need 0-30. 5 bits are needed to represent 0-30 days. To represent all possible months in a year, 12 months, and starting with 0, you need 0-11. 4 bits are needed to represent 0-11 months. This means there are 7 bits left out of the 16 bit structure for years. 7 bits can represent a maximum of 127 years. Therefore, starting in 1948, the maximum range is 1948 + 127 = 2075.
Money version 2.0 handles 4-digits dates in the following manner:
Money version 2.0 handles 2-digit dates in the following manner: If YY is 00-47, it is considered 20xx (2000-2047) If YY 48-99, it is considered 19xx (1948-1999) Microsoft Money supports the QIF data transfer protocol developed by Intuit. Most versions of QIF have represented dates using a 2-digit year format. While the data stored in Money is Year 2000 compliant, Money needs to use a heuristic to determine the best two-digit date to use when importing to or exporting from the QIF format. In some versions, QIF uses an apostrophe to denote dates in the 2000s. For example: 1/31’01 indicates January 31, 2001. Presented below is a table describing how Money interprets QIF data ranges:
| ||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
| - | ||||||||||||||||||||||
| None | ||||||||||||||||||||||
| Windows 95 or later; Windows NT 4.0 Service Pack 4 or later | ||||||||||||||||||||||
| Operating system clock is not advanced beyond 2038 | ||||||||||||||||||||||
| 28 Sep 1999 | ||||||||||||||||||||||
|
Description of how the product accepts dates:
Money 2000 uses the OLE Automation "DATE" data type. This is represented as a double (8-byte floating point) value. The whole-number portion represents the number of days since Dec 30th, 1899 A.D. The fractional portion (which Money does not use very often) represents the fraction of a day to indicate a time (e.g., 0.25=6:00am, 0.5=noon, etc.). Dates that have no time representation are stored with no fractional part. For example, January 1st, 1900 would be represented as the number 2.0.
Users can enter dates in Money as a 2-digit representation (e.g., 99, 00, 01) or a 4-digit representation (e.g., 1999, 2000, 2001). Example: in the check register, the user can enter the date 1/2/00. This date is recognized as 1/2/2000. The logic that Money uses for converting 2-digit years into the actual year varies depending on what Date data entry field is in question. Money generally uses a heuristic that compares the 2-digit year that has been entered to the current year. If the Year+1900 is more than 33 years in the past, then Money assumes that the date is in the future and uses Year+2000. Dates are displayed in Microsoft Money consistent with the Windows date format setting. Years can be displayed as either 2 or 4-digit. OFX and OFC Money transmits date information to (and receives from) OFX and OFC using a 4-digit format (YYYYMMDD) within the operational date range for the Money product.
Checkfree: The Checkfree/ISC/NPC 4.2 specification (dated 1/23/1996) specifies the data format for communications with Checkfree. Checkfree uses six numeric digits to represent dates as YYMMDD. Money and Checkfree exchange and translate 2-digit years during Online Banking connections using the following algorithm: If YY = 00 it is considered 20__ __ If YY < 93, it is considered 20__ (e.g., 2092) If YY >= 93, it is considered 19__ (e.g., 1993) Applying this formula, the operational date range for Money in connection with online bill payment services with Checkfree is 1/1/1993 to 12/31/2092. ANSER-SPC Money transmits date information to (and receives from) ANSER-SPC without year information. When Money receives date information without year, Money uses a heuristic rule and treats either as current year or as previous year. If the day in the downloaded statements is in the future, Money assumes that the date is from last year. Microsoft Money supports the QIF data transfer protocol developed by Intuit. Most versions of QIF have represented dates using a two-digit year format. While the data stored in Money is Y2K compliant, Money needs to use a heuristic to determine the best two-digit date to use when importing to or exporting from the QIF format. The heuristic compares the 2-digit year that is being imported to the current year. If the Year+1900 is more than 33 years in the past, then Money assumes that the date is in the future and uses Year+2000. In some versions, QIF uses an apostrophe to denote specific date ranges (for example 1/31’01 ). In Quicken 98, it is used to indicate the years from 1900 – 1949 and 2050 – 2099. In versions prior to Quicken 98, in Quicken 99, and in Money v. 4.0 and up, an apostrophe is used to indicate the years from 2000 – 2099. Dates in the apostrophe format will be interpreted with the same heuristic as other valid QIF date formats. Users must use the Windows date format of MM/dd/YY format when they import and export QIF files using US Money 2000. This mm/dd/yy system date format is required when importing and exporting QIF according to Intuit’s Quicken QIF Y2K statement. Presented below is a table describing how Money interprets QIF data ranges: US Money2000:
* These date ranges will change as Today’s date changes according to the heuristic Money uses.
| ||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
| - | ||||||||||||||||||||||
| None | ||||||||||||||||||||||
| Windows 95 or later; Windows NT 4.0 Service Pack 4 or later | ||||||||||||||||||||||
| Operating system clock is not advanced beyond 2038 | ||||||||||||||||||||||
| 28 Sep 1999 | ||||||||||||||||||||||
|
Description of how the product accepts dates:
Money 2000 uses the OLE Automation "DATE" data type. This is represented as a double (8-byte floating point) value. The whole-number portion represents the number of days since Dec 30th, 1899 A.D. The fractional portion (which Money does not use very often) represents the fraction of a day to indicate a time (e.g., 0.25=6:00am, 0.5=noon, etc.). Dates that have no time representation are stored with no fractional part. For example, January 1st, 1900 would be represented as the number 2.0.
Users can enter dates in Money as a 2-digit representation (e.g., 99, 00, 01) or a 4-digit representation (e.g., 1999, 2000, 2001). Example: in the check register, the user can enter the date 1/2/00. This date is recognized as 1/2/2000. The logic that Money uses for converting 2-digit years into the actual year varies depending on what Date data entry field is in question. Money generally uses a heuristic that compares the 2-digit year that has been entered to the current year. If the Year+1900 is more than 33 years in the past, then Money assumes that the date is in the future and uses Year+2000. Dates are displayed in Microsoft Money consistent with the Windows date format setting. Years can be displayed as either 2 or 4-digit. OFX and OFC Money transmits date information to (and receives from) OFX and OFC using a 4-digit format (YYYYMMDD) within the operational date range for the Money product.
Checkfree: The Checkfree/ISC/NPC 4.2 specification (dated 1/23/1996) specifies the data format for communications with Checkfree. Checkfree uses six numeric digits to represent dates as YYMMDD. Money and Checkfree exchange and translate 2-digit years during Online Banking connections using the following algorithm: If YY = 00 it is considered 20__ __ If YY < 93, it is considered 20__ (e.g., 2092) If YY >= 93, it is considered 19__ (e.g., 1993) Applying this formula, the operational date range for Money in connection with online bill payment services with Checkfree is 1/1/1993 to 12/31/2092. ANSER-SPC Money transmits date information to (and receives from) ANSER-SPC without year information. When Money receives date information without year, Money uses a heuristic rule and treats either as current year or as previous year. If the day in the downloaded statements is in the future, Money assumes that the date is from last year. Microsoft Money supports the QIF data transfer protocol developed by Intuit. Most versions of QIF have represented dates using a two-digit year format. While the data stored in Money is Y2K compliant, Money needs to use a heuristic to determine the best two-digit date to use when importing to or exporting from the QIF format. The heuristic compares the 2-digit year that is being imported to the current year. If the Year+1900 is more than 33 years in the past, then Money assumes that the date is in the future and uses Year+2000. In some versions, QIF uses an apostrophe to denote specific date ranges (for example 1/31’01 ). In Quicken 98, it is used to indicate the years from 1900 – 1949 and 2050 – 2099. In versions prior to Quicken 98, in Quicken 99, and in Money v. 4.0 and up, an apostrophe is used to indicate the years from 2000 – 2099. Dates in the apostrophe format will be interpreted with the same heuristic as other valid QIF date formats. Users must use the Windows date format of MM/dd/YY format when they import and export QIF files using US Money 2000. This mm/dd/yy system date format is required when importing and exporting QIF according to Intuit’s Quicken QIF Y2K statement. Presented below is a table describing how Money interprets QIF data ranges: US Money2000:
* These date ranges will change as Today’s date changes according to the heuristic Money uses.
| ||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
| - | ||||||||||||||||||||||
| None | ||||||||||||||||||||||
| Windows 95 or later; Windows NT 4.0 Service Pack 4 or later | ||||||||||||||||||||||
| Operating system clock is not advanced beyond 2038 | ||||||||||||||||||||||
| 28 Sep 1999 | ||||||||||||||||||||||
|
Description of how the product accepts dates:
Money 2000 uses the OLE Automation "DATE" data type. This is represented as a double (8-byte floating point) value. The whole-number portion represents the number of days since Dec 30th, 1899 A.D. The fractional portion (which Money does not use very often) represents the fraction of a day to indicate a time (e.g., 0.25=6:00am, 0.5=noon, etc.). Dates that have no time representation are stored with no fractional part. For example, January 1st, 1900 would be represented as the number 2.0.
Users can enter dates in Money as a 2-digit representation (e.g., 99, 00, 01) or a 4-digit representation (e.g., 1999, 2000, 2001). Example: in the check register, the user can enter the date 1/2/00. This date is recognized as 1/2/2000. The logic that Money uses for converting 2-digit years into the actual year varies depending on what Date data entry field is in question. Money generally uses a heuristic that compares the 2-digit year that has been entered to the current year. If the Year+1900 is more than 33 years in the past, then Money assumes that the date is in the future and uses Year+2000. Dates are displayed in Microsoft Money consistent with the Windows date format setting. Years can be displayed as either 2 or 4-digit. OFX and OFC Money transmits date information to (and receives from) OFX and OFC using a 4-digit format (YYYYMMDD) within the operational date range for the Money product.
Checkfree: The Checkfree/ISC/NPC 4.2 specification (dated 1/23/1996) specifies the data format for communications with Checkfree. Checkfree uses six numeric digits to represent dates as YYMMDD. Money and Checkfree exchange and translate 2-digit years during Online Banking connections using the following algorithm: If YY = 00 it is considered 20__ __ If YY < 93, it is considered 20__ (e.g., 2092) If YY >= 93, it is considered 19__ (e.g., 1993) Applying this formula, the operational date range for Money in connection with online bill payment services with Checkfree is 1/1/1993 to 12/31/2092. ANSER-SPC Money transmits date information to (and receives from) ANSER-SPC without year information. When Money receives date information without year, Money uses a heuristic rule and treats either as current year or as previous year. If the day in the downloaded statements is in the future, Money assumes that the date is from last year. Microsoft Money supports the QIF data transfer protocol developed by Intuit. Most versions of QIF have represented dates using a two-digit year format. While the data stored in Money is Y2K compliant, Money needs to use a heuristic to determine the best two-digit date to use when importing to or exporting from the QIF format. The heuristic compares the 2-digit year that is being imported to the current year. If the Year+1900 is more than 33 years in the past, then Money assumes that the date is in the future and uses Year+2000. In some versions, QIF uses an apostrophe to denote specific date ranges (for example 1/31’01 ). In Quicken 98, it is used to indicate the years from 1900 – 1949 and 2050 – 2099. In versions prior to Quicken 98, in Quicken 99, and in Money v. 4.0 and up, an apostrophe is used to indicate the years from 2000 – 2099. Dates in the apostrophe format will be interpreted with the same heuristic as other valid QIF date formats. Users must use the Windows date format of MM/dd/YY format when they import and export QIF files using US Money 2000. This mm/dd/yy system date format is required when importing and exporting QIF according to Intuit’s Quicken QIF Y2K statement. Presented below is a table describing how Money interprets QIF data ranges: US Money2000:
* These date ranges will change as Today’s date changes according to the heuristic Money uses.
| ||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
| - | ||||||||||||||||||||||
| None | ||||||||||||||||||||||
| Windows 95 or later; Windows NT 4.0 Service Pack 4 or later | ||||||||||||||||||||||
| Operating system clock is not advanced beyond 2038 | ||||||||||||||||||||||
| 28 Sep 1999 | ||||||||||||||||||||||
|
Description of how the product accepts dates:
Money 2000 uses the OLE Automation "DATE" data type. This is represented as a double (8-byte floating point) value. The whole-number portion represents the number of days since Dec 30th, 1899 A.D. The fractional portion (which Money does not use very often) represents the fraction of a day to indicate a time (e.g., 0.25=6:00am, 0.5=noon, etc.). Dates that have no time representation are stored with no fractional part. For example, January 1st, 1900 would be represented as the number 2.0.
Users can enter dates in Money as a 2-digit representation (e.g., 99, 00, 01) or a 4-digit representation (e.g., 1999, 2000, 2001). Example: in the check register, the user can enter the date 1/2/00. This date is recognized as 1/2/2000. The logic that Money uses for converting 2-digit years into the actual year varies depending on what Date data entry field is in question. Money generally uses a heuristic that compares the 2-digit year that has been entered to the current year. If the Year+1900 is more than 33 years in the past, then Money assumes that the date is in the future and uses Year+2000. Dates are displayed in Microsoft Money consistent with the Windows date format setting. Years can be displayed as either 2 or 4-digit. OFX and OFC Money transmits date information to (and receives from) OFX and OFC using a 4-digit format (YYYYMMDD) within the operational date range for the Money product.
Checkfree: The Checkfree/ISC/NPC 4.2 specification (dated 1/23/1996) specifies the data format for communications with Checkfree. Checkfree uses six numeric digits to represent dates as YYMMDD. Money and Checkfree exchange and translate 2-digit years during Online Banking connections using the following algorithm: If YY = 00 it is considered 20__ __ If YY < 93, it is considered 20__ (e.g., 2092) If YY >= 93, it is considered 19__ (e.g., 1993) Applying this formula, the operational date range for Money in connection with online bill payment services with Checkfree is 1/1/1993 to 12/31/2092. ANSER-SPC Money transmits date information to (and receives from) ANSER-SPC without year information. When Money receives date information without year, Money uses a heuristic rule and treats either as current year or as previous year. If the day in the downloaded statements is in the future, Money assumes that the date is from last year. Microsoft Money supports the QIF data transfer protocol developed by Intuit. Most versions of QIF have represented dates using a two-digit year format. While the data stored in Money is Y2K compliant, Money needs to use a heuristic to determine the best two-digit date to use when importing to or exporting from the QIF format. The heuristic compares the 2-digit year that is being imported to the current year. If the Year+1900 is more than 33 years in the past, then Money assumes that the date is in the future and uses Year+2000. In some versions, QIF uses an apostrophe to denote specific date ranges (for example 1/31’01 ). In Quicken 98, it is used to indicate the years from 1900 – 1949 and 2050 – 2099. In versions prior to Quicken 98, in Quicken 99, and in Money v. 4.0 and up, an apostrophe is used to indicate the years from 2000 – 2099. Dates in the apostrophe format will be interpreted with the same heuristic as other valid QIF date formats. Users must use the Windows date format of MM/dd/YY format when they import and export QIF files using US Money 2000. This mm/dd/yy system date format is required when importing and exporting QIF according to Intuit’s Quicken QIF Y2K statement. Presented below is a table describing how Money interprets QIF data ranges: US Money2000:
* These date ranges will change as Today’s date changes according to the heuristic Money uses.
| ||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
| - | ||||||||||||||||||||||
| None | ||||||||||||||||||||||
| Windows 95 or later; Windows NT 4.0 Service Pack 4 or later | ||||||||||||||||||||||
| Operating system clock is not advanced beyond 2038 | ||||||||||||||||||||||
| 28 Sep 1999 | ||||||||||||||||||||||
|
Description of how the product accepts dates:
Money 2000 uses the OLE Automation "DATE" data type. This is represented as a double (8-byte floating point) value. The whole-number portion represents the number of days since Dec 30th, 1899 A.D. The fractional portion (which Money does not use very often) represents the fraction of a day to indicate a time (e.g., 0.25=6:00am, 0.5=noon, etc.). Dates that have no time representation are stored with no fractional part. For example, January 1st, 1900 would be represented as the number 2.0.
Users can enter dates in Money as a 2-digit representation (e.g., 99, 00, 01) or a 4-digit representation (e.g., 1999, 2000, 2001). Example: in the check register, the user can enter the date 1/2/00. This date is recognized as 1/2/2000. The logic that Money uses for converting 2-digit years into the actual year varies depending on what Date data entry field is in question. Money generally uses a heuristic that compares the 2-digit year that has been entered to the current year. If the Year+1900 is more than 33 years in the past, then Money assumes that the date is in the future and uses Year+2000. Dates are displayed in Microsoft Money consistent with the Windows date format setting. Years can be displayed as either 2 or 4-digit. OFX and OFC Money transmits date information to (and receives from) OFX and OFC using a 4-digit format (YYYYMMDD) within the operational date range for the Money product.
Checkfree: The Checkfree/ISC/NPC 4.2 specification (dated 1/23/1996) specifies the data format for communications with Checkfree. Checkfree uses six numeric digits to represent dates as YYMMDD. Money and Checkfree exchange and translate 2-digit years during Online Banking connections using the following algorithm: If YY = 00 it is considered 20__ __ If YY < 93, it is considered 20__ (e.g., 2092) If YY >= 93, it is considered 19__ (e.g., 1993) Applying this formula, the operational date range for Money in connection with online bill payment services with Checkfree is 1/1/1993 to 12/31/2092. ANSER-SPC Money transmits date information to (and receives from) ANSER-SPC without year information. When Money receives date information without year, Money uses a heuristic rule and treats either as current year or as previous year. If the day in the downloaded statements is in the future, Money assumes that the date is from last year. Microsoft Money supports the QIF data transfer protocol developed by Intuit. Most versions of QIF have represented dates using a two-digit year format. While the data stored in Money is Y2K compliant, Money needs to use a heuristic to determine the best two-digit date to use when importing to or exporting from the QIF format. The heuristic compares the 2-digit year that is being imported to the current year. If the Year+1900 is more than 33 years in the past, then Money assumes that the date is in the future and uses Year+2000. In some versions, QIF uses an apostrophe to denote specific date ranges (for example 1/31’01 ). In Quicken 98, it is used to indicate the years from 1900 – 1949 and 2050 – 2099. In versions prior to Quicken 98, in Quicken 99, and in Money v. 4.0 and up, an apostrophe is used to indicate the years from 2000 – 2099. Dates in the apostrophe format will be interpreted with the same heuristic as other valid QIF date formats. Users must use the Windows date format of MM/dd/YY format when they import and export QIF files using US Money 2000. This mm/dd/yy system date format is required when importing and exporting QIF according to Intuit’s Quicken QIF Y2K statement. Presented below is a table describing how Money interprets QIF data ranges: US Money2000:
* These date ranges will change as Today’s date changes according to the heuristic Money uses.
| ||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
| - | ||||||||||||||||||||||
| None | ||||||||||||||||||||||
| Windows 95 or later; Windows NT 4.0 Service Pack 4 or later | ||||||||||||||||||||||
| Operating system clock is not advanced beyond 2038 | ||||||||||||||||||||||
| 28 Sep 1999 | ||||||||||||||||||||||
|
Description of how the product accepts dates:
Money 2000 uses the OLE Automation "DATE" data type. This is represented as a double (8-byte floating point) value. The whole-number portion represents the number of days since Dec 30th, 1899 A.D. The fractional portion (which Money does not use very often) represents the fraction of a day to indicate a time (e.g., 0.25=6:00am, 0.5=noon, etc.). Dates that have no time representation are stored with no fractional part. For example, January 1st, 1900 would be represented as the number 2.0.
Users can enter dates in Money as a 2-digit representation (e.g., 99, 00, 01) or a 4-digit representation (e.g., 1999, 2000, 2001). Example: in the check register, the user can enter the date 1/2/00. This date is recognized as 1/2/2000. The logic that Money uses for converting 2-digit years into the actual year varies depending on what Date data entry field is in question. Money generally uses a heuristic that compares the 2-digit year that has been entered to the current year. If the Year+1900 is more than 33 years in the past, then Money assumes that the date is in the future and uses Year+2000. Dates are displayed in Microsoft Money consistent with the Windows date format setting. Years can be displayed as either 2 or 4-digit. OFX and OFC Money transmits date information to (and receives from) OFX and OFC using a 4-digit format (YYYYMMDD) within the operational date range for the Money product.
Checkfree: The Checkfree/ISC/NPC 4.2 specification (dated 1/23/1996) specifies the data format for communications with Checkfree. Checkfree uses six numeric digits to represent dates as YYMMDD. Money and Checkfree exchange and translate 2-digit years during Online Banking connections using the following algorithm: If YY = 00 it is considered 20__ __ If YY < 93, it is considered 20__ (e.g., 2092) If YY >= 93, it is considered 19__ (e.g., 1993) Applying this formula, the operational date range for Money in connection with online bill payment services with Checkfree is 1/1/1993 to 12/31/2092. ANSER-SPC Money transmits date information to (and receives from) ANSER-SPC without year information. When Money receives date information without year, Money uses a heuristic rule and treats either as current year or as previous year. If the day in the downloaded statements is in the future, Money assumes that the date is from last year. Microsoft Money supports the QIF data transfer protocol developed by Intuit. Most versions of QIF have represented dates using a two-digit year format. While the data stored in Money is Y2K compliant, Money needs to use a heuristic to determine the best two-digit date to use when importing to or exporting from the QIF format. The heuristic compares the 2-digit year that is being imported to the current year. If the Year+1900 is more than 33 years in the past, then Money assumes that the date is in the future and uses Year+2000. In some versions, QIF uses an apostrophe to denote specific date ranges (for example 1/31’01 ). In Quicken 98, it is used to indicate the years from 1900 – 1949 and 2050 – 2099. In versions prior to Quicken 98, in Quicken 99, and in Money v. 4.0 and up, an apostrophe is used to indicate the years from 2000 – 2099. Dates in the apostrophe format will be interpreted with the same heuristic as other valid QIF date formats. Users must use the Windows date format of MM/dd/YY format when they import and export QIF files using US Money 2000. This mm/dd/yy system date format is required when importing and exporting QIF according to Intuit’s Quicken QIF Y2K statement. Presented below is a table describing how Money interprets QIF data ranges: US Money2000:
* These date ranges will change as Today’s date changes according to the heuristic Money uses.
| ||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
| - | ||||||||||||||||||||||
| None | ||||||||||||||||||||||
| Windows 95 or later; Windows NT 4.0 Service Pack 4 or later | ||||||||||||||||||||||
| Operating system clock is not advanced beyond 2038 | ||||||||||||||||||||||
| 28 Sep 1999 | ||||||||||||||||||||||
|
Description of how the product accepts dates:
Money 2000 uses the OLE Automation "DATE" data type. This is represented as a double (8-byte floating point) value. The whole-number portion represents the number of days since Dec 30th, 1899 A.D. The fractional portion (which Money does not use very often) represents the fraction of a day to indicate a time (e.g., 0.25=6:00am, 0.5=noon, etc.). Dates that have no time representation are stored with no fractional part. For example, January 1st, 1900 would be represented as the number 2.0.
Users can enter dates in Money as a 2-digit representation (e.g., 99, 00, 01) or a 4-digit representation (e.g., 1999, 2000, 2001). Example: in the check register, the user can enter the date 1/2/00. This date is recognized as 1/2/2000. The logic that Money uses for converting 2-digit years into the actual year varies depending on what Date data entry field is in question. Money generally uses a heuristic that compares the 2-digit year that has been entered to the current year. If the Year+1900 is more than 33 years in the past, then Money assumes that the date is in the future and uses Year+2000. Dates are displayed in Microsoft Money consistent with the Windows date format setting. Years can be displayed as either 2 or 4-digit. OFX and OFC Money transmits date information to (and receives from) OFX and OFC using a 4-digit format (YYYYMMDD) within the operational date range for the Money product.
Checkfree: The Checkfree/ISC/NPC 4.2 specification (dated 1/23/1996) specifies the data format for communications with Checkfree. Checkfree uses six numeric digits to represent dates as YYMMDD. Money and Checkfree exchange and translate 2-digit years during Online Banking connections using the following algorithm: If YY = 00 it is considered 20__ __ If YY < 93, it is considered 20__ (e.g., 2092) If YY >= 93, it is considered 19__ (e.g., 1993) Applying this formula, the operational date range for Money in connection with online bill payment services with Checkfree is 1/1/1993 to 12/31/2092. ANSER-SPC Money transmits date information to (and receives from) ANSER-SPC without year information. When Money receives date information without year, Money uses a heuristic rule and treats either as current year or as previous year. If the day in the downloaded statements is in the future, Money assumes that the date is from last year. Microsoft Money supports the QIF data transfer protocol developed by Intuit. Most versions of QIF have represented dates using a two-digit year format. While the data stored in Money is Y2K compliant, Money needs to use a heuristic to determine the best two-digit date to use when importing to or exporting from the QIF format. The heuristic compares the 2-digit year that is being imported to the current year. If the Year+1900 is more than 33 years in the past, then Money assumes that the date is in the future and uses Year+2000. In some versions, QIF uses an apostrophe to denote specific date ranges (for example 1/31’01 ). In Quicken 98, it is used to indicate the years from 1900 – 1949 and 2050 – 2099. In versions prior to Quicken 98, in Quicken 99, and in Money v. 4.0 and up, an apostrophe is used to indicate the years from 2000 – 2099. Dates in the apostrophe format will be interpreted with the same heuristic as other valid QIF date formats. Users must use the Windows date format of MM/dd/YY format when they import and export QIF files using US Money 2000. This mm/dd/yy system date format is required when importing and exporting QIF according to Intuit’s Quicken QIF Y2K statement. Presented below is a table describing how Money interprets QIF data ranges: US Money2000:
* These date ranges will change as Today’s date changes according to the heuristic Money uses.
| ||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
| - | ||||||||||||||||||||||
| None | ||||||||||||||||||||||
| Windows 95 or later; Windows NT 4.0 Service Pack 4 or later | ||||||||||||||||||||||
| Operating system clock is not advanced beyond 2038 | ||||||||||||||||||||||
| 28 Sep 1999 | ||||||||||||||||||||||
|
Description of how the product accepts dates:
Money 2000 uses the OLE Automation "DATE" data type. This is represented as a double (8-byte floating point) value. The whole-number portion represents the number of days since Dec 30th, 1899 A.D. The fractional portion (which Money does not use very often) represents the fraction of a day to indicate a time (e.g., 0.25=6:00am, 0.5=noon, etc.). Dates that have no time representation are stored with no fractional part. For example, January 1st, 1900 would be represented as the number 2.0.
Users can enter dates in Money as a 2-digit representation (e.g., 99, 00, 01) or a 4-digit representation (e.g., 1999, 2000, 2001). Example: in the check register, the user can enter the date 1/2/00. This date is recognized as 1/2/2000. The logic that Money uses for converting 2-digit years into the actual year varies depending on what Date data entry field is in question. Money generally uses a heuristic that compares the 2-digit year that has been entered to the current year. If the Year+1900 is more than 33 years in the past, then Money assumes that the date is in the future and uses Year+2000. Dates are displayed in Microsoft Money consistent with the Windows date format setting. Years can be displayed as either 2 or 4-digit. OFX and OFC Money transmits date information to (and receives from) OFX and OFC using a 4-digit format (YYYYMMDD) within the operational date range for the Money product.
Checkfree: The Checkfree/ISC/NPC 4.2 specification (dated 1/23/1996) specifies the data format for communications with Checkfree. Checkfree uses six numeric digits to represent dates as YYMMDD. Money and Checkfree exchange and translate 2-digit years during Online Banking connections using the following algorithm: If YY = 00 it is considered 20__ __ If YY < 93, it is considered 20__ (e.g., 2092) If YY >= 93, it is considered 19__ (e.g., 1993) Applying this formula, the operational date range for Money in connection with online bill payment services with Checkfree is 1/1/1993 to 12/31/2092. ANSER-SPC Money transmits date information to (and receives from) ANSER-SPC without year information. When Money receives date information without year, Money uses a heuristic rule and treats either as current year or as previous year. If the day in the downloaded statements is in the future, Money assumes that the date is from last year. Microsoft Money supports the QIF data transfer protocol developed by Intuit. Most versions of QIF have represented dates using a two-digit year format. While the data stored in Money is Y2K compliant, Money needs to use a heuristic to determine the best two-digit date to use when importing to or exporting from the QIF format. The heuristic compares the 2-digit year that is being imported to the current year. If the Year+1900 is more than 33 years in the past, then Money assumes that the date is in the future and uses Year+2000. In some versions, QIF uses an apostrophe to denote specific date ranges (for example 1/31’01 ). In Quicken 98, it is used to indicate the years from 1900 – 1949 and 2050 – 2099. In versions prior to Quicken 98, in Quicken 99, and in Money v. 4.0 and up, an apostrophe is used to indicate the years from 2000 – 2099. Dates in the apostrophe format will be interpreted with the same heuristic as other valid QIF date formats. Users must use the Windows date format of MM/dd/YY format when they import and export QIF files using US Money 2000. This mm/dd/yy system date format is required when importing and exporting QIF according to Intuit’s Quicken QIF Y2K statement. Presented below is a table describing how Money interprets QIF data ranges: US Money2000:
* These date ranges will change as Today’s date changes according to the heuristic Money uses.
| ||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
| - | ||||||||||||||||||||
| none | ||||||||||||||||||||
| Windows 3.1 or later | ||||||||||||||||||||
| Operating system clock is not advanced beyond 2038 | ||||||||||||||||||||
| 14 Aug 1999 | ||||||||||||||||||||
|
Operational Range for Data: Generally 1/1/1948 – 12/31/2075 but1/1/1993 - 12/31/2075 for certain online banking services. How the product accepts dates: Money 3.0 accepts dates from 1/1/1948 through 12/31/2075. It uses a field oriented date structure with 16 bits to represent dates:
These date values are zero-based, which means to represent all possible days in a month, 31 days, and starting with 0, you need 0-30. 5 bits are needed to represent 0-30 days. To represent all possible months in a year, 12 months, and starting with 0, you need 0-11. 4 bits are needed to represent 0-11 months. This means there are 7 bits left out of the 16-bit structure for years. 7 bits can represent a maximum of 127 years. Therefore, starting in 1948, the maximum range is 1948 + 127 = 2075.
Money version 3.0 accepts 4-digits dates in the following manner:
Money version 3.0 accepts 2-digit dates in the following manner: If YY is 00-47, it is considered 20xx (2000-2047). If YY is 48-99, it is considered 19xx (1948-1999). Checkfree/ISC/NPC: Checkfree/ISC/NPC’s specification specifies the data format for communications with Checkfree. Checkfree uses six numeric digits to represent dates as YYMMDD. Money and Checkfree exchange and translate 2-digit years during Online Banking connections using the following algorithm: If YY = 00, it is considered 2000 If YY < 93, it is considered 20xx (e.g., 2092) If YY >= 93, it is considered 19xx (e.g., 1993) Applying this formula, the operational date range for Money in connection with online bill payment services with Checkfree is 1/1/1993 to 12/31/2075. Microsoft Money supports the QIF data transfer protocol developed by Intuit. Most versions of QIF have represented dates using a two-digit year format. While the data stored in Money is Year 2000 compliant, Money needs to use a heuristic to determine the best two-digit date to use when importing to or exporting from the QIF format. The rules of this heuristic are listed in the table below. In some versions, QIF uses an apostrophe to denote specific date ranges (for example 1/31’01). In Quicken 98, it is used to indicate the years from 1900 – 1949 and 2050 – 2099. In versions prior to Quicken 98, in Quicken 99, and in Money v. 4.0 and up, an apostrophe is used to indicate the years from 2000 – 2099. When Money v. 3.0 was released, it did not support the apostrophe format in QIF. Presented below is a table describing how Money interprets QIF data ranges:
| ||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
| - | ||||||||||||||||||||
| none | ||||||||||||||||||||
| Windows 3.1 or later | ||||||||||||||||||||
| Operating system clock is not advanced beyond 2038 | ||||||||||||||||||||
| 15 Aug 1999 | ||||||||||||||||||||
|
Operational Range for Data: Generally 1/1/1948 – 12/31/2075 but1/1/1993 - 12/31/2075 for certain online banking services. How the product accepts dates: Money 3.0 accepts dates from 1/1/1948 through 12/31/2075. It uses a field oriented date structure with 16 bits to represent dates:
These date values are zero-based, which means to represent all possible days in a month, 31 days, and starting with 0, you need 0-30. 5 bits are needed to represent 0-30 days. To represent all possible months in a year, 12 months, and starting with 0, you need 0-11. 4 bits are needed to represent 0-11 months. This means there are 7 bits left out of the 16-bit structure for years. 7 bits can represent a maximum of 127 years. Therefore, starting in 1948, the maximum range is 1948 + 127 = 2075.
Money version 3.0 accepts 4-digits dates in the following manner:
Money version 3.0 accepts 2-digit dates in the following manner: If YY is 00-47, it is considered 20xx (2000-2047). If YY is 48-99, it is considered 19xx (1948-1999). Checkfree/ISC/NPC: Checkfree/ISC/NPC’s specification specifies the data format for communications with Checkfree. Checkfree uses six numeric digits to represent dates as YYMMDD. Money and Checkfree exchange and translate 2-digit years during Online Banking connections using the following algorithm: If YY = 00, it is considered 2000 If YY < 93, it is considered 20xx (e.g., 2092) If YY >= 93, it is considered 19xx (e.g., 1993) Applying this formula, the operational date range for Money in connection with online bill payment services with Checkfree is 1/1/1993 to 12/31/2075. Microsoft Money supports the QIF data transfer protocol developed by Intuit. Most versions of QIF have represented dates using a two-digit year format. While the data stored in Money is Year 2000 compliant, Money needs to use a heuristic to determine the best two-digit date to use when importing to or exporting from the QIF format. The rules of this heuristic are listed in the table below. In some versions, QIF uses an apostrophe to denote specific date ranges (for example 1/31’01). In Quicken 98, it is used to indicate the years from 1900 – 1949 and 2050 – 2099. In versions prior to Quicken 98, in Quicken 99, and in Money v. 4.0 and up, an apostrophe is used to indicate the years from 2000 – 2099. When Money v. 3.0 was released, it did not support the apostrophe format in QIF. Presented below is a table describing how Money interprets QIF data ranges:
| ||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
| - | ||||||||||||||||||||
| none | ||||||||||||||||||||
| Windows 3.1 or later | ||||||||||||||||||||
| Operating system clock is not advanced beyond 2038 | ||||||||||||||||||||
| 15 Aug 1999 | ||||||||||||||||||||
|
Operational Range for Data: Generally 1/1/1948 – 12/31/2075 but1/1/1993 - 12/31/2075 for certain online banking services. How the product accepts dates: Money 3.0 accepts dates from 1/1/1948 through 12/31/2075. It uses a field oriented date structure with 16 bits to represent dates:
These date values are zero-based, which means to represent all possible days in a month, 31 days, and starting with 0, you need 0-30. 5 bits are needed to represent 0-30 days. To represent all possible months in a year, 12 months, and starting with 0, you need 0-11. 4 bits are needed to represent 0-11 months. This means there are 7 bits left out of the 16-bit structure for years. 7 bits can represent a maximum of 127 years. Therefore, starting in 1948, the maximum range is 1948 + 127 = 2075.
Money version 3.0 accepts 4-digits dates in the following manner:
Money version 3.0 accepts 2-digit dates in the following manner: If YY is 00-47, it is considered 20xx (2000-2047). If YY is 48-99, it is considered 19xx (1948-1999). Checkfree/ISC/NPC: Checkfree/ISC/NPC’s specification specifies the data format for communications with Checkfree. Checkfree uses six numeric digits to represent dates as YYMMDD. Money and Checkfree exchange and translate 2-digit years during Online Banking connections using the following algorithm: If YY = 00, it is considered 2000 If YY < 93, it is considered 20xx (e.g., 2092) If YY >= 93, it is considered 19xx (e.g., 1993) Applying this formula, the operational date range for Money in connection with online bill payment services with Checkfree is 1/1/1993 to 12/31/2075. Microsoft Money supports the QIF data transfer protocol developed by Intuit. Most versions of QIF have represented dates using a two-digit year format. While the data stored in Money is Year 2000 compliant, Money needs to use a heuristic to determine the best two-digit date to use when importing to or exporting from the QIF format. The rules of this heuristic are listed in the table below. In some versions, QIF uses an apostrophe to denote specific date ranges (for example 1/31’01). In Quicken 98, it is used to indicate the years from 1900 – 1949 and 2050 – 2099. In versions prior to Quicken 98, in Quicken 99, and in Money v. 4.0 and up, an apostrophe is used to indicate the years from 2000 – 2099. When Money v. 3.0 was released, it did not support the apostrophe format in QIF. Presented below is a table describing how Money interprets QIF data ranges:
| ||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
| - | ||||||||||||||||||||
| none | ||||||||||||||||||||
| Windows 3.1 or later | ||||||||||||||||||||
| Operating system clock is not advanced beyond 2038 | ||||||||||||||||||||
| 15 Aug 1999 | ||||||||||||||||||||
|
Operational Range for Data: Generally 1/1/1948 – 12/31/2075 but1/1/1993 - 12/31/2075 for certain online banking services. How the product accepts dates: Money 3.0 accepts dates from 1/1/1948 through 12/31/2075. It uses a field oriented date structure with 16 bits to represent dates:
These date values are zero-based, which means to represent all possible days in a month, 31 days, and starting with 0, you need 0-30. 5 bits are needed to represent 0-30 days. To represent all possible months in a year, 12 months, and starting with 0, you need 0-11. 4 bits are needed to represent 0-11 months. This means there are 7 bits left out of the 16-bit structure for years. 7 bits can represent a maximum of 127 years. Therefore, starting in 1948, the maximum range is 1948 + 127 = 2075.
Money version 3.0 accepts 4-digits dates in the following manner:
Money version 3.0 accepts 2-digit dates in the following manner: If YY is 00-47, it is considered 20xx (2000-2047). If YY is 48-99, it is considered 19xx (1948-1999). Checkfree/ISC/NPC: Checkfree/ISC/NPC’s specification specifies the data format for communications with Checkfree. Checkfree uses six numeric digits to represent dates as YYMMDD. Money and Checkfree exchange and translate 2-digit years during Online Banking connections using the following algorithm: If YY = 00, it is considered 2000 If YY < 93, it is considered 20xx (e.g., 2092) If YY >= 93, it is considered 19xx (e.g., 1993) Applying this formula, the operational date range for Money in connection with online bill payment services with Checkfree is 1/1/1993 to 12/31/2075. Microsoft Money supports the QIF data transfer protocol developed by Intuit. Most versions of QIF have represented dates using a two-digit year format. While the data stored in Money is Year 2000 compliant, Money needs to use a heuristic to determine the best two-digit date to use when importing to or exporting from the QIF format. The rules of this heuristic are listed in the table below. In some versions, QIF uses an apostrophe to denote specific date ranges (for example 1/31’01). In Quicken 98, it is used to indicate the years from 1900 – 1949 and 2050 – 2099. In versions prior to Quicken 98, in Quicken 99, and in Money v. 4.0 and up, an apostrophe is used to indicate the years from 2000 – 2099. When Money v. 3.0 was released, it did not support the apostrophe format in QIF. Presented below is a table describing how Money interprets QIF data ranges:
| ||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
| - | ||||||||||||||||||||
| none | ||||||||||||||||||||
| Windows 3.1 or later | ||||||||||||||||||||
| Operating system clock is not advanced beyond 2038 | ||||||||||||||||||||
| 15 Aug 1999 | ||||||||||||||||||||
|
Operational Range for Data: Generally 1/1/1948 – 12/31/2075 but1/1/1993 - 12/31/2075 for certain online banking services. How the product accepts dates: Money 3.0 accepts dates from 1/1/1948 through 12/31/2075. It uses a field oriented date structure with 16 bits to represent dates:
These date values are zero-based, which means to represent all possible days in a month, 31 days, and starting with 0, you need 0-30. 5 bits are needed to represent 0-30 days. To represent all possible months in a year, 12 months, and starting with 0, you need 0-11. 4 bits are needed to represent 0-11 months. This means there are 7 bits left out of the 16-bit structure for years. 7 bits can represent a maximum of 127 years. Therefore, starting in 1948, the maximum range is 1948 + 127 = 2075.
Money version 3.0 accepts 4-digits dates in the following manner:
Money version 3.0 accepts 2-digit dates in the following manner: If YY is 00-47, it is considered 20xx (2000-2047). If YY is 48-99, it is considered 19xx (1948-1999). Checkfree/ISC/NPC: Checkfree/ISC/NPC’s specification specifies the data format for communications with Checkfree. Checkfree uses six numeric digits to represent dates as YYMMDD. Money and Checkfree exchange and translate 2-digit years during Online Banking connections using the following algorithm: If YY = 00, it is considered 2000 If YY < 93, it is considered 20xx (e.g., 2092) If YY >= 93, it is considered 19xx (e.g., 1993) Applying this formula, the operational date range for Money in connection with online bill payment services with Checkfree is 1/1/1993 to 12/31/2075. Microsoft Money supports the QIF data transfer protocol developed by Intuit. Most versions of QIF have represented dates using a two-digit year format. While the data stored in Money is Year 2000 compliant, Money needs to use a heuristic to determine the best two-digit date to use when importing to or exporting from the QIF format. The rules of this heuristic are listed in the table below. In some versions, QIF uses an apostrophe to denote specific date ranges (for example 1/31’01). In Quicken 98, it is used to indicate the years from 1900 – 1949 and 2050 – 2099. In versions prior to Quicken 98, in Quicken 99, and in Money v. 4.0 and up, an apostrophe is used to indicate the years from 2000 – 2099. When Money v. 3.0 was released, it did not support the apostrophe format in QIF. Presented below is a table describing how Money interprets QIF data ranges:
| ||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
| - | ||||||||||||||||||
| None. | ||||||||||||||||||
| Windows 95, or Windows NT 3.51 or later. | ||||||||||||||||||
| Operating system clock is not advanced beyond 2038. | ||||||||||||||||||
| 15 Aug 1999 | ||||||||||||||||||
|
Operational Range for Data: Generally 1/1/1948 – 12/31/2075 but,1/1/1993 - 12/31/2075 for certain online banking Services How the product accepts dates: Money version 4.0 accepts dates from January 1, 1948 through December 31, 2075. It uses a field oriented date structure with 16 bits to represent dates:
These date values are zero-based, which means to represent all possible days in a month, 31 days, and starting with 0, you need 0-30. 5 bits are needed to represent 0-30 days. To represent all possible months in a year, 12 months, and starting with 0, you need 0-11. 4 bits are needed to represent 0-11 months. This means there are 7 bits left out of the 16-bit structure for years. 7 bits can represent a maximum of 127 years. Therefore, starting in 1948, the maximum range is 1948 + 127 = 2075.
Money version 4.0 accepts 4-digits dates in the following manner:
Money version 4.0 accepts 2-digit dates in the following manner: If YY is 00-47, it is considered 20xx (2000-2047). If YY is 48-99, it is considered 19xx (1948-1999).
Checkfree/ISC/NPC: Checkfree/ISC/NPC’s specification specifies the data format for communications with Checkfree. Checkfree uses six numeric digits to represent dates as YYMMDD. Money and Checkfree exchange and translate 2-digit years during Online Banking connections using the following algorithm: If YY = 00, it is considered 2000 If YY < 93, it is considered 20xx (e.g., 2092) If YY >= 93, it is considered 19xx (e.g., 1993) Applying this formula, the operational date range for Money in connection with online bill payment services with Checkfree is 1/1/1993 to 12/31/2075. Microsoft Money supports the QIF data transfer protocol developed by Intuit. Most versions of QIF have represented dates using a two-digit year format. While the data stored in Money is Year 2000 compliant, Money needs to use a heuristic to determine the best two-digit date to use when importing to or exporting from the QIF format. The rules of this heuristic are listed in the table below. In some versions, QIF uses an apostrophe to denote specific date ranges (for example 1/31’01). In Quicken 98, it is used to indicate the years from 1900 – 1949 and 2050 – 2099. In versions prior to Quicken 98, in Quicken 99, and in Money v. 4.0 and up, an apostrophe is used to indicate the years from 2000 – 2099. When Money v. 4.0 was released, this latter interpretation of the apostrophe format was standard. Presented below is a table describing how Money interprets QIF data ranges:
| ||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
| - | ||||||||||||||||||
| none | ||||||||||||||||||
| Windows 95, or Windows NT 3.51 or later | ||||||||||||||||||
| Operating system clock is not advanced beyond 2038 | ||||||||||||||||||
| 15 Aug 1999 | ||||||||||||||||||
|
Operational Range for Data: Generally 1/1/1948 – 12/31/2075 but,1/1/1993 - 12/31/2075 for certain online banking Services How the product accepts dates: Money version 4.0 accepts dates from January 1, 1948 through December 31, 2075. It uses a field oriented date structure with 16 bits to represent dates:
These date values are zero-based, which means to represent all possible days in a month, 31 days, and starting with 0, you need 0-30. 5 bits are needed to represent 0-30 days. To represent all possible months in a year, 12 months, and starting with 0, you need 0-11. 4 bits are needed to represent 0-11 months. This means there are 7 bits left out of the 16-bit structure for years. 7 bits can represent a maximum of 127 years. Therefore, starting in 1948, the maximum range is 1948 + 127 = 2075.
Money version 4.0 accepts 4-digits dates in the following manner:
Money version 4.0 accepts 2-digit dates in the following manner: If YY is 00-47, it is considered 20xx (2000-2047). If YY is 48-99, it is considered 19xx (1948-1999).
Checkfree/ISC/NPC: Checkfree/ISC/NPC’s specification specifies the data format for communications with Checkfree. Checkfree uses six numeric digits to represent dates as YYMMDD. Money and Checkfree exchange and translate 2-digit years during Online Banking connections using the following algorithm: If YY = 00, it is considered 2000 If YY < 93, it is considered 20xx (e.g., 2092) If YY >= 93, it is considered 19xx (e.g., 1993) Applying this formula, the operational date range for Money in connection with online bill payment services with Checkfree is 1/1/1993 to 12/31/2075. Microsoft Money supports the QIF data transfer protocol developed by Intuit. Most versions of QIF have represented dates using a two-digit year format. While the data stored in Money is Year 2000 compliant, Money needs to use a heuristic to determine the best two-digit date to use when importing to or exporting from the QIF format. The rules of this heuristic are listed in the table below. In some versions, QIF uses an apostrophe to denote specific date ranges (for example 1/31’01). In Quicken 98, it is used to indicate the years from 1900 – 1949 and 2050 – 2099. In versions prior to Quicken 98, in Quicken 99, and in Money v. 4.0 and up, an apostrophe is used to indicate the years from 2000 – 2099. When Money v. 4.0 was released, this latter interpretation of the apostrophe format was standard. Presented below is a table describing how Money interprets QIF data ranges:
| ||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
| - | ||||||||||||||||||
| none | ||||||||||||||||||
| Windows 95, or Windows NT 3.51 or later | ||||||||||||||||||
| Operating system clock is not advanced beyond 2038 | ||||||||||||||||||
| 15 Aug 1999 | ||||||||||||||||||
|
Operational Range for Data: Generally 1/1/1948 – 12/31/2075 but,1/1/1993 - 12/31/2075 for certain online banking Services How the product accepts dates: Money version 4.0 accepts dates from January 1, 1948 through December 31, 2075. It uses a field oriented date structure with 16 bits to represent dates:
These date values are zero-based, which means to represent all possible days in a month, 31 days, and starting with 0, you need 0-30. 5 bits are needed to represent 0-30 days. To represent all possible months in a year, 12 months, and starting with 0, you need 0-11. 4 bits are needed to represent 0-11 months. This means there are 7 bits left out of the 16-bit structure for years. 7 bits can represent a maximum of 127 years. Therefore, starting in 1948, the maximum range is 1948 + 127 = 2075.
Money version 4.0 accepts 4-digits dates in the following manner:
Money version 4.0 accepts 2-digit dates in the following manner: If YY is 00-47, it is considered 20xx (2000-2047). If YY is 48-99, it is considered 19xx (1948-1999).
Checkfree/ISC/NPC: Checkfree/ISC/NPC’s specification specifies the data format for communications with Checkfree. Checkfree uses six numeric digits to represent dates as YYMMDD. Money and Checkfree exchange and translate 2-digit years during Online Banking connections using the following algorithm: If YY = 00, it is considered 2000 If YY < 93, it is considered 20xx (e.g., 2092) If YY >= 93, it is considered 19xx (e.g., 1993) Applying this formula, the operational date range for Money in connection with online bill payment services with Checkfree is 1/1/1993 to 12/31/2075. Microsoft Money supports the QIF data transfer protocol developed by Intuit. Most versions of QIF have represented dates using a two-digit year format. While the data stored in Money is Year 2000 compliant, Money needs to use a heuristic to determine the best two-digit date to use when importing to or exporting from the QIF format. The rules of this heuristic are listed in the table below. In some versions, QIF uses an apostrophe to denote specific date ranges (for example 1/31’01). In Quicken 98, it is used to indicate the years from 1900 – 1949 and 2050 – 2099. In versions prior to Quicken 98, in Quicken 99, and in Money v. 4.0 and up, an apostrophe is used to indicate the years from 2000 – 2099. When Money v. 4.0 was released, this latter interpretation of the apostrophe format was standard. Presented below is a table describing how Money interprets QIF data ranges:
| ||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
| - | ||||||||||||||||||
| none | ||||||||||||||||||
| Windows 95, or Windows NT 3.51 or later | ||||||||||||||||||
| Operating system clock is not advanced beyond 2038 | ||||||||||||||||||
| 15 Aug 1999 | ||||||||||||||||||
|
Operational Range for Data: Generally 1/1/1948 – 12/31/2075 but,1/1/1993 - 12/31/2075 for certain online banking Services How the product accepts dates: Money version 4.0 accepts dates from January 1, 1948 through December 31, 2075. It uses a field oriented date structure with 16 bits to represent dates:
These date values are zero-based, which means to represent all possible days in a month, 31 days, and starting with 0, you need 0-30. 5 bits are needed to represent 0-30 days. To represent all possible months in a year, 12 months, and starting with 0, you need 0-11. 4 bits are needed to represent 0-11 months. This means there are 7 bits left out of the 16-bit structure for years. 7 bits can represent a maximum of 127 years. Therefore, starting in 1948, the maximum range is 1948 + 127 = 2075.
Money version 4.0 accepts 4-digits dates in the following manner:
Money version 4.0 accepts 2-digit dates in the following manner: If YY is 00-47, it is considered 20xx (2000-2047). If YY is 48-99, it is considered 19xx (1948-1999).
Checkfree/ISC/NPC: Checkfree/ISC/NPC’s specification specifies the data format for communications with Checkfree. Checkfree uses six numeric digits to represent dates as YYMMDD. Money and Checkfree exchange and translate 2-digit years during Online Banking connections using the following algorithm: If YY = 00, it is considered 2000 If YY < 93, it is considered 20xx (e.g., 2092) If YY >= 93, it is considered 19xx (e.g., 1993) Applying this formula, the operational date range for Money in connection with online bill payment services with Checkfree is 1/1/1993 to 12/31/2075. Microsoft Money supports the QIF data transfer protocol developed by Intuit. Most versions of QIF have represented dates using a two-digit year format. While the data stored in Money is Year 2000 compliant, Money needs to use a heuristic to determine the best two-digit date to use when importing to or exporting from the QIF format. The rules of this heuristic are listed in the table below. In some versions, QIF uses an apostrophe to denote specific date ranges (for example 1/31’01). In Quicken 98, it is used to indicate the years from 1900 – 1949 and 2050 – 2099. In versions prior to Quicken 98, in Quicken 99, and in Money v. 4.0 and up, an apostrophe is used to indicate the years from 2000 – 2099. When Money v. 4.0 was released, this latter interpretation of the apostrophe format was standard. Presented below is a table describing how Money interprets QIF data ranges:
| ||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
| - | ||||||||||||||||||
| None. | ||||||||||||||||||
| Windows 95, or Windows NT 3.51 or later. | ||||||||||||||||||
| Operating system clock is not advanced beyond 2038. | ||||||||||||||||||
| 15 Aug 1999 | ||||||||||||||||||
|
Operational Range for Data: Generally 1/1/1948 – 12/31/2075 but,1/1/1993 - 12/31/2075 for certain online banking Services How the product accepts dates: Money version 4.0 accepts dates from January 1, 1948 through December 31, 2075. It uses a field oriented date structure with 16 bits to represent dates:
These date values are zero-based, which means to represent all possible days in a month, 31 days, and starting with 0, you need 0-30. 5 bits are needed to represent 0-30 days. To represent all possible months in a year, 12 months, and starting with 0, you need 0-11. 4 bits are needed to represent 0-11 months. This means there are 7 bits left out of the 16-bit structure for years. 7 bits can represent a maximum of 127 years. Therefore, starting in 1948, the maximum range is 1948 + 127 = 2075.
Money version 4.0 accepts 4-digits dates in the following manner:
Money version 4.0 accepts 2-digit dates in the following manner: If YY is 00-47, it is considered 20xx (2000-2047). If YY is 48-99, it is considered 19xx (1948-1999).
Checkfree/ISC/NPC: Checkfree/ISC/NPC’s specification specifies the data format for communications with Checkfree. Checkfree uses six numeric digits to represent dates as YYMMDD. Money and Checkfree exchange and translate 2-digit years during Online Banking connections using the following algorithm: If YY = 00, it is considered 2000 If YY < 93, it is considered 20xx (e.g., 2092) If YY >= 93, it is considered 19xx (e.g., 1993) Applying this formula, the operational date range for Money in connection with online bill payment services with Checkfree is 1/1/1993 to 12/31/2075. Microsoft Money supports the QIF data transfer protocol developed by Intuit. Most versions of QIF have represented dates using a two-digit year format. While the data stored in Money is Year 2000 compliant, Money needs to use a heuristic to determine the best two-digit date to use when importing to or exporting from the QIF format. The rules of this heuristic are listed in the table below. In some versions, QIF uses an apostrophe to denote specific date ranges (for example 1/31’01). In Quicken 98, it is used to indicate the years from 1900 – 1949 and 2050 – 2099. In versions prior to Quicken 98, in Quicken 99, and in Money v. 4.0 and up, an apostrophe is used to indicate the years from 2000 – 2099. When Money v. 4.0 was released, this latter interpretation of the apostrophe format was standard. Presented below is a table describing how Money interprets QIF data ranges:
| ||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
| - | ||||||||||||||||||
| None. | ||||||||||||||||||
| Windows 95, or Windows NT 3.51 or later. | ||||||||||||||||||
| Operating system clock is not advanced beyond 2038. | ||||||||||||||||||
| 15 Aug 1999 | ||||||||||||||||||
|
Operational Range for Data: Generally 1/1/1948 – 12/31/2075 but,1/1/1993 - 12/31/2075 for certain online banking Services How the product accepts dates: Money version 4.0 accepts dates from January 1, 1948 through December 31, 2075. It uses a field oriented date structure with 16 bits to represent dates:
These date values are zero-based, which means to represent all possible days in a month, 31 days, and starting with 0, you need 0-30. 5 bits are needed to represent 0-30 days. To represent all possible months in a year, 12 months, and starting with 0, you need 0-11. 4 bits are needed to represent 0-11 months. This means there are 7 bits left out of the 16-bit structure for years. 7 bits can represent a maximum of 127 years. Therefore, starting in 1948, the maximum range is 1948 + 127 = 2075.
Money version 4.0 accepts 4-digits dates in the following manner:
Money version 4.0 accepts 2-digit dates in the following manner: If YY is 00-47, it is considered 20xx (2000-2047). If YY is 48-99, it is considered 19xx (1948-1999).
Checkfree/ISC/NPC: Checkfree/ISC/NPC’s specification specifies the data format for communications with Checkfree. Checkfree uses six numeric digits to represent dates as YYMMDD. Money and Checkfree exchange and translate 2-digit years during Online Banking connections using the following algorithm: If YY = 00, it is considered 2000 If YY < 93, it is considered 20xx (e.g., 2092) If YY >= 93, it is considered 19xx (e.g., 1993) Applying this formula, the operational date range for Money in connection with online bill payment services with Checkfree is 1/1/1993 to 12/31/2075. Microsoft Money supports the QIF data transfer protocol developed by Intuit. Most versions of QIF have represented dates using a two-digit year format. While the data stored in Money is Year 2000 compliant, Money needs to use a heuristic to determine the best two-digit date to use when importing to or exporting from the QIF format. The rules of this heuristic are listed in the table below. In some versions, QIF uses an apostrophe to denote specific date ranges (for example 1/31’01). In Quicken 98, it is used to indicate the years from 1900 – 1949 and 2050 – 2099. In versions prior to Quicken 98, in Quicken 99, and in Money v. 4.0 and up, an apostrophe is used to indicate the years from 2000 – 2099. When Money v. 4.0 was released, this latter interpretation of the apostrophe format was standard. Presented below is a table describing how Money interprets QIF data ranges:
| ||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
| - | ||||||||||||||||||
| None. | ||||||||||||||||||
| Windows 95, or Windows NT 3.51 or later. | ||||||||||||||||||
| Operating system clock is not advanced beyond 2038. | ||||||||||||||||||
| 15 Aug 1999 | ||||||||||||||||||
|
Operational Range for Data: Generally January 1, 1948 – 12/31/2075 but,1/1/1993 - 12/31/2075 for certain online banking services. Description of how the product accepts dates: Money 97 accepts dates from January 1, 1948 through December 31, 2075. It uses a field oriented date structure with 16 bits to represent dates:
These date values are zero-based, which means to represent all possible days in a month, 31 days, and starting with 0, you need 0-30. 5 bits are needed to represent 0-30 days. To represent all possible months in a year, 12 months, and starting with 0, you need 0-11. 4 bits are needed to represent 0-11 months. This means there are 7 bits left out of the 16 bit structure for years. 7 bits can represent a maximum of 127 years. Therefore, starting in 1948, the maximum range is 1948 + 127 = 2075.
Money 97 accepts 4-digits dates in the following manner:
Money 97 accepts 2-digit dates in the following manner: If YY is 00-47, it is considered 20xx (2000-2047). If YY is 48-99, it is considered 19xx (1948-1999).
OFC and Visa: Money transmits date information to (and receives from) OFX, OFC and VISA using a 4-digit format (YYYYMMDD) within the operational date range for the Money product.
Checkfree/ISC/NPC: Checkfree/ISC/NPC’s specification specifies the data format for communications with Checkfree. Checkfree uses six numeric digits to represent dates as YYMMDD. Money and Checkfree exchange and translate 2-digit years (YY) during Online Banking connections using the following algorithm: If YY = 00, it is considered 2000 If YY < 93, it is considered 20xx (e.g., 2092) If YY >= 93, it is considered 19xx (e.g., 1993) Applying this formula, the operational date range for Money in connection with online bill payment services with Checkfree is 1/1/1993 to 12/31/2075.
Microsoft Money supports the QIF data transfer protocol developed by Intuit. Most versions of QIF have represented dates using a 2-digit year format. While the data stored in Money is Year 2000 compliant, Money needs to use a heuristic to determine the best 2-digit date to use when importing to or exporting from the QIF format. The rules of this heuristic are listed in the table below. In some versions, QIF uses an apostrophe to denote specific date ranges (for example 1/31'01). In Quicken 98, it is used to indicate the years from 1900 – 1949 and 2050 – 2099. In versions prior to Quicken 98, in Quicken 99, and in Money v. 4.0 and up, an apostrophe is used to indicate the years from 2000 – 2099. When Money97 was released, this latter interpretation of the apostrophe format was standard. Presented below is a table describing how Money interprets QIF data ranges:
| ||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
| - | ||||||||||||||||||
| none | ||||||||||||||||||
| Windows 95, or Windows NT 3.51 or later | ||||||||||||||||||
| Operating System Clock is not advanced beyond 2038 | ||||||||||||||||||
| 15 Aug 1999 | ||||||||||||||||||
|
Operational Range for Data: Generally January 1, 1948 – 12/31/2075 but,1/1/1993 - 12/31/2075 for certain online banking services. Description of how the product accepts dates: Money 97 accepts dates from January 1, 1948 through December 31, 2075. It uses a field oriented date structure with 16 bits to represent dates:
These date values are zero-based, which means to represent all possible days in a month, 31 days, and starting with 0, you need 0-30. 5 bits are needed to represent 0-30 days. To represent all possible months in a year, 12 months, and starting with 0, you need 0-11. 4 bits are needed to represent 0-11 months. This means there are 7 bits left out of the 16 bit structure for years. 7 bits can represent a maximum of 127 years. Therefore, starting in 1948, the maximum range is 1948 + 127 = 2075.
Money 97 accepts 4-digits dates in the following manner:
Money 97 accepts 2-digit dates in the following manner: If YY is 00-47, it is considered 20xx (2000-2047). If YY is 48-99, it is considered 19xx (1948-1999).
OFC and Visa: Money transmits date information to (and receives from) OFX, OFC and VISA using a 4-digit format (YYYYMMDD) within the operational date range for the Money product.
Checkfree/ISC/NPC: Checkfree/ISC/NPC’s specification specifies the data format for communications with Checkfree. Checkfree uses six numeric digits to represent dates as YYMMDD. Money and Checkfree exchange and translate 2-digit years (YY) during Online Banking connections using the following algorithm: If YY = 00, it is considered 2000 If YY < 93, it is considered 20xx (e.g., 2092) If YY >= 93, it is considered 19xx (e.g., 1993) Applying this formula, the operational date range for Money in connection with online bill payment services with Checkfree is 1/1/1993 to 12/31/2075.
Microsoft Money supports the QIF data transfer protocol developed by Intuit. Most versions of QIF have represented dates using a 2-digit year format. While the data stored in Money is Year 2000 compliant, Money needs to use a heuristic to determine the best 2-digit date to use when importing to or exporting from the QIF format. The rules of this heuristic are listed in the table below. In some versions, QIF uses an apostrophe to denote specific date ranges (for example 1/31'01). In Quicken 98, it is used to indicate the years from 1900 – 1949 and 2050 – 2099. In versions prior to Quicken 98, in Quicken 99, and in Money v. 4.0 and up, an apostrophe is used to indicate the years from 2000 – 2099. When Money97 was released, this latter interpretation of the apostrophe format was standard. Presented below is a table describing how Money interprets QIF data ranges:
| ||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
| - | ||||||||||||||||||
| none | ||||||||||||||||||
| Windows 95, or Windows NT 3.51 or later | ||||||||||||||||||
| Operating System Clock is not advanced beyond 2038 | ||||||||||||||||||
| 15 Aug 1999 | ||||||||||||||||||
|
Operational Range for Data: Generally January 1, 1948 – 12/31/2075 but,1/1/1993 - 12/31/2075 for certain online banking services. Description of how the product accepts dates: Money 97 accepts dates from January 1, 1948 through December 31, 2075. It uses a field oriented date structure with 16 bits to represent dates:
These date values are zero-based, which means to represent all possible days in a month, 31 days, and starting with 0, you need 0-30. 5 bits are needed to represent 0-30 days. To represent all possible months in a year, 12 months, and starting with 0, you need 0-11. 4 bits are needed to represent 0-11 months. This means there are 7 bits left out of the 16 bit structure for years. 7 bits can represent a maximum of 127 years. Therefore, starting in 1948, the maximum range is 1948 + 127 = 2075.
Money 97 accepts 4-digits dates in the following manner:
Money 97 accepts 2-digit dates in the following manner: If YY is 00-47, it is considered 20xx (2000-2047). If YY is 48-99, it is considered 19xx (1948-1999).
OFC and Visa: Money transmits date information to (and receives from) OFX, OFC and VISA using a 4-digit format (YYYYMMDD) within the operational date range for the Money product.
Checkfree/ISC/NPC: Checkfree/ISC/NPC’s specification specifies the data format for communications with Checkfree. Checkfree uses six numeric digits to represent dates as YYMMDD. Money and Checkfree exchange and translate 2-digit years (YY) during Online Banking connections using the following algorithm: If YY = 00, it is considered 2000 If YY < 93, it is considered 20xx (e.g., 2092) If YY >= 93, it is considered 19xx (e.g., 1993) Applying this formula, the operational date range for Money in connection with online bill payment services with Checkfree is 1/1/1993 to 12/31/2075.
Microsoft Money supports the QIF data transfer protocol developed by Intuit. Most versions of QIF have represented dates using a 2-digit year format. While the data stored in Money is Year 2000 compliant, Money needs to use a heuristic to determine the best 2-digit date to use when importing to or exporting from the QIF format. The rules of this heuristic are listed in the table below. In some versions, QIF uses an apostrophe to denote specific date ranges (for example 1/31'01). In Quicken 98, it is used to indicate the years from 1900 – 1949 and 2050 – 2099. In versions prior to Quicken 98, in Quicken 99, and in Money v. 4.0 and up, an apostrophe is used to indicate the years from 2000 – 2099. When Money97 was released, this latter interpretation of the apostrophe format was standard. Presented below is a table describing how Money interprets QIF data ranges:
| ||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
| - | ||||||||||||||||||
| none | ||||||||||||||||||
| Windows 95, or Windows NT 3.51 or later | ||||||||||||||||||
| Operating System Clock is not advanced beyond 2038 | ||||||||||||||||||
| 15 Aug 1999 | ||||||||||||||||||
|
Operational Range for Data: Generally January 1, 1948 – 12/31/2075 but,1/1/1993 - 12/31/2075 for certain online banking services. Description of how the product accepts dates: Money 97 accepts dates from January 1, 1948 through December 31, 2075. It uses a field oriented date structure with 16 bits to represent dates:
These date values are zero-based, which means to represent all possible days in a month, 31 days, and starting with 0, you need 0-30. 5 bits are needed to represent 0-30 days. To represent all possible months in a year, 12 months, and starting with 0, you need 0-11. 4 bits are needed to represent 0-11 months. This means there are 7 bits left out of the 16 bit structure for years. 7 bits can represent a maximum of 127 years. Therefore, starting in 1948, the maximum range is 1948 + 127 = 2075.
Money 97 accepts 4-digits dates in the following manner:
Money 97 accepts 2-digit dates in the following manner: If YY is 00-47, it is considered 20xx (2000-2047). If YY is 48-99, it is considered 19xx (1948-1999).
OFC and Visa: Money transmits date information to (and receives from) OFX, OFC and VISA using a 4-digit format (YYYYMMDD) within the operational date range for the Money product.
Checkfree/ISC/NPC: Checkfree/ISC/NPC’s specification specifies the data format for communications with Checkfree. Checkfree uses six numeric digits to represent dates as YYMMDD. Money and Checkfree exchange and translate 2-digit years (YY) during Online Banking connections using the following algorithm: If YY = 00, it is considered 2000 If YY < 93, it is considered 20xx (e.g., 2092) If YY >= 93, it is considered 19xx (e.g., 1993) Applying this formula, the operational date range for Money in connection with online bill payment services with Checkfree is 1/1/1993 to 12/31/2075.
Microsoft Money supports the QIF data transfer protocol developed by Intuit. Most versions of QIF have represented dates using a 2-digit year format. While the data stored in Money is Year 2000 compliant, Money needs to use a heuristic to determine the best 2-digit date to use when importing to or exporting from the QIF format. The rules of this heuristic are listed in the table below. In some versions, QIF uses an apostrophe to denote specific date ranges (for example 1/31'01). In Quicken 98, it is used to indicate the years from 1900 – 1949 and 2050 – 2099. In versions prior to Quicken 98, in Quicken 99, and in Money v. 4.0 and up, an apostrophe is used to indicate the years from 2000 – 2099. When Money97 was released, this latter interpretation of the apostrophe format was standard. Presented below is a table describing how Money interprets QIF data ranges:
| ||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
| - | ||||||||||||||||||
| none | ||||||||||||||||||
| Windows 95, or Windows NT 3.51 or later | ||||||||||||||||||
| Operating System Clock is not advanced beyond 2038 | ||||||||||||||||||
| 15 Aug 1999 | ||||||||||||||||||
|
Operational Range for Data: Generally January 1, 1948 – 12/31/2075 but,1/1/1993 - 12/31/2075 for certain online banking services. Description of how the product accepts dates: Money 97 accepts dates from January 1, 1948 through December 31, 2075. It uses a field oriented date structure with 16 bits to represent dates:
These date values are zero-based, which means to represent all possible days in a month, 31 days, and starting with 0, you need 0-30. 5 bits are needed to represent 0-30 days. To represent all possible months in a year, 12 months, and starting with 0, you need 0-11. 4 bits are needed to represent 0-11 months. This means there are 7 bits left out of the 16 bit structure for years. 7 bits can represent a maximum of 127 years. Therefore, starting in 1948, the maximum range is 1948 + 127 = 2075.
Money 97 accepts 4-digits dates in the following manner:
Money 97 accepts 2-digit dates in the following manner: If YY is 00-47, it is considered 20xx (2000-2047). If YY is 48-99, it is considered 19xx (1948-1999).
OFC and Visa: Money transmits date information to (and receives from) OFX, OFC and VISA using a 4-digit format (YYYYMMDD) within the operational date range for the Money product.
Checkfree/ISC/NPC: Checkfree/ISC/NPC’s specification specifies the data format for communications with Checkfree. Checkfree uses six numeric digits to represent dates as YYMMDD. Money and Checkfree exchange and translate 2-digit years (YY) during Online Banking connections using the following algorithm: If YY = 00, it is considered 2000 If YY < 93, it is considered 20xx (e.g., 2092) If YY >= 93, it is considered 19xx (e.g., 1993) Applying this formula, the operational date range for Money in connection with online bill payment services with Checkfree is 1/1/1993 to 12/31/2075.
Microsoft Money supports the QIF data transfer protocol developed by Intuit. Most versions of QIF have represented dates using a 2-digit year format. While the data stored in Money is Year 2000 compliant, Money needs to use a heuristic to determine the best 2-digit date to use when importing to or exporting from the QIF format. The rules of this heuristic are listed in the table below. In some versions, QIF uses an apostrophe to denote specific date ranges (for example 1/31'01). In Quicken 98, it is used to indicate the years from 1900 – 1949 and 2050 – 2099. In versions prior to Quicken 98, in Quicken 99, and in Money v. 4.0 and up, an apostrophe is used to indicate the years from 2000 – 2099. When Money97 was released, this latter interpretation of the apostrophe format was standard. Presented below is a table describing how Money interprets QIF data ranges:
| ||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
| - | ||||||||||||||||||
| none | ||||||||||||||||||
| Windows 95, or Windows NT 3.51 or later | ||||||||||||||||||
| Operating System Clock is not advanced beyond 2038 | ||||||||||||||||||
| 15 Aug 1999 | ||||||||||||||||||
|
Operational Range for Data: Generally January 1, 1948 – 12/31/2075 but,1/1/1993 - 12/31/2075 for certain online banking services. Description of how the product accepts dates: Money 97 accepts dates from January 1, 1948 through December 31, 2075. It uses a field oriented date structure with 16 bits to represent dates:
These date values are zero-based, which means to represent all possible days in a month, 31 days, and starting with 0, you need 0-30. 5 bits are needed to represent 0-30 days. To represent all possible months in a year, 12 months, and starting with 0, you need 0-11. 4 bits are needed to represent 0-11 months. This means there are 7 bits left out of the 16 bit structure for years. 7 bits can represent a maximum of 127 years. Therefore, starting in 1948, the maximum range is 1948 + 127 = 2075.
Money 97 accepts 4-digits dates in the following manner:
Money 97 accepts 2-digit dates in the following manner: If YY is 00-47, it is considered 20xx (2000-2047). If YY is 48-99, it is considered 19xx (1948-1999).
OFC and Visa: Money transmits date information to (and receives from) OFX, OFC and VISA using a 4-digit format (YYYYMMDD) within the operational date range for the Money product.
Checkfree/ISC/NPC: Checkfree/ISC/NPC’s specification specifies the data format for communications with Checkfree. Checkfree uses six numeric digits to represent dates as YYMMDD. Money and Checkfree exchange and translate 2-digit years (YY) during Online Banking connections using the following algorithm: If YY = 00, it is considered 2000 If YY < 93, it is considered 20xx (e.g., 2092) If YY >= 93, it is considered 19xx (e.g., 1993) Applying this formula, the operational date range for Money in connection with online bill payment services with Checkfree is 1/1/1993 to 12/31/2075.
Microsoft Money supports the QIF data transfer protocol developed by Intuit. Most versions of QIF have represented dates using a 2-digit year format. While the data stored in Money is Year 2000 compliant, Money needs to use a heuristic to determine the best 2-digit date to use when importing to or exporting from the QIF format. The rules of this heuristic are listed in the table below. In some versions, QIF uses an apostrophe to denote specific date ranges (for example 1/31'01). In Quicken 98, it is used to indicate the years from 1900 – 1949 and 2050 – 2099. In versions prior to Quicken 98, in Quicken 99, and in Money v. 4.0 and up, an apostrophe is used to indicate the years from 2000 – 2099. When Money97 was released, this latter interpretation of the apostrophe format was standard. Presented below is a table describing how Money interprets QIF data ranges:
| ||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
| - | ||||||||||||||||||
| none | ||||||||||||||||||
| Windows 95, or Windows NT 3.51 or later | ||||||||||||||||||
| Operating System Clock is not advanced beyond 2038 | ||||||||||||||||||
| 15 Aug 1999 | ||||||||||||||||||
|
Operational Range for Data: Generally January 1, 1948 – 12/31/2075 but,1/1/1993 - 12/31/2075 for certain online banking services. Description of how the product accepts dates: Money 97 accepts dates from January 1, 1948 through December 31, 2075. It uses a field oriented date structure with 16 bits to represent dates:
These date values are zero-based, which means to represent all possible days in a month, 31 days, and starting with 0, you need 0-30. 5 bits are needed to represent 0-30 days. To represent all possible months in a year, 12 months, and starting with 0, you need 0-11. 4 bits are needed to represent 0-11 months. This means there are 7 bits left out of the 16 bit structure for years. 7 bits can represent a maximum of 127 years. Therefore, starting in 1948, the maximum range is 1948 + 127 = 2075.
Money 97 accepts 4-digits dates in the following manner:
Money 97 accepts 2-digit dates in the following manner: If YY is 00-47, it is considered 20xx (2000-2047). If YY is 48-99, it is considered 19xx (1948-1999).
OFC and Visa: Money transmits date information to (and receives from) OFX, OFC and VISA using a 4-digit format (YYYYMMDD) within the operational date range for the Money product.
Checkfree/ISC/NPC: Checkfree/ISC/NPC’s specification specifies the data format for communications with Checkfree. Checkfree uses six numeric digits to represent dates as YYMMDD. Money and Checkfree exchange and translate 2-digit years (YY) during Online Banking connections using the following algorithm: If YY = 00, it is considered 2000 If YY < 93, it is considered 20xx (e.g., 2092) If YY >= 93, it is considered 19xx (e.g., 1993) Applying this formula, the operational date range for Money in connection with online bill payment services with Checkfree is 1/1/1993 to 12/31/2075.
Microsoft Money supports the QIF data transfer protocol developed by Intuit. Most versions of QIF have represented dates using a 2-digit year format. While the data stored in Money is Year 2000 compliant, Money needs to use a heuristic to determine the best 2-digit date to use when importing to or exporting from the QIF format. The rules of this heuristic are listed in the table below. In some versions, QIF uses an apostrophe to denote specific date ranges (for example 1/31'01). In Quicken 98, it is used to indicate the years from 1900 – 1949 and 2050 – 2099. In versions prior to Quicken 98, in Quicken 99, and in Money v. 4.0 and up, an apostrophe is used to indicate the years from 2000 – 2099. When Money97 was released, this latter interpretation of the apostrophe format was standard. Presented below is a table describing how Money interprets QIF data ranges:
| ||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
| - | ||||||||||||||||||||
| None | ||||||||||||||||||||
| Windows 95, or Windows NT 4 (no specific Service Pack is required, though Service Pack 3 is recommended) | ||||||||||||||||||||
| Operating system clock is not advanced beyond 2038 | ||||||||||||||||||||
| 08 Apr 1999 | ||||||||||||||||||||
|
Operational Range for Data: Generally January 1, 1900 – December 31, 2200 butJanuary 1, 1993 – December 31, 2092 for certain online banking Services How the product accepts dates:
Microsoft Money supports the QIF data transfer protocol developed by Intuit. Most versions of QIF have represented dates using a 2-digit year format. While the data stored in Money is Year 2000 compliant, Money needs to use a heuristic to determine the best 2-digit date to use when importing to or exporting from the QIF format. The rules of this heuristic are listed in the table below. In some versions, QIF uses an apostrophe to denote specific date ranges (for example 1/31'01). In Quicken 98, it is used to indicate the years from 1900 – 1949 and 2050 – 2099. In versions prior to Quicken 98, in Quicken 99, and in Money v. 4.0 and up, an apostrophe is used to indicate the years from 2000 – 2099. When Money98 was released, this latter interpretation of the apostrophe format was standard. Presented below is a table describing how Money interprets QIF data ranges:
| ||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
| - | ||||||||||||||||||||
| none | ||||||||||||||||||||
| Windows 95, or Windows NT 4 (no specific Service Pack is required, though Service Pack 3 is recommended) | ||||||||||||||||||||
| Operating system clock is not advanced beyond 2038 | ||||||||||||||||||||
| 08 Apr 1999 | ||||||||||||||||||||
|
Operational Range for Data: Generally January 1, 1900 – December 31, 2200 butJanuary 1, 1993 – December 31, 2092 for certain online banking Services How the product accepts dates:
Money 98 uses the OLE Automation "DATE" data type. This is represented as a double (8-byte floating point) value. The whole-number portion represents the number of days since Dec 30, 1899 A.D. The decimal portion (which Money does not use very often) represents the fraction of a day to indicate a time (e.g., 0.25=6:00am, 0.5=noon, etc.). Dates that have no time representation are stored with no decimal part. For example, January 1, 1900 would be represented as the number 2.0.
Users can enter dates in Money as a 2-digit representation (e.g., 99, 00, 01) or a 4-digit representation (e.g., 1999, 2000, 2001). Example: in the check register, the user can enter the date 1/2/00. This date is recognized as 1/2/2000. The logic that Money uses for converting 2-digit years into the actual year varies depending on what Date data entry field is in question. Money generally uses a heuristic that compares the 2-digit year that has been entered to the current year. If the Year+1900 is more than 33 years in the past, then Money assumes that the date is in the future and uses Year+2000. Dates are displayed in Microsoft Money consistent with the Windows date format setting. Years can be displayed as either 2 or 4-digit.
OFX, OFC, Visa. Money transmits date information to (and receives from) OFX, OFC and VISA using a 4-digit format (YYYYMMDD) within the operational date range for the Money product.
Checkfree: The Checkfree/ISC/NPC 4.2 specification (dated 1/23/1996) specifies the data format for communications with Checkfree. Checkfree uses six numeric digits to represent dates as YYMMDD. Money and Checkfree exchange and translate 2-digit years during Online Banking connections using the following algorithm: If YY = 00, it is considered 2000 If YY < 93, it is considered 20xx (e.g., 2092) If YY >= 93, it is considered 19xx (e.g., 1993) Applying this formula, the operational date range for Money in connection with online bill payment services with Checkfree is 1/1/1993 to 12/31/2092.
International (BTX/MTL) Money operates with two locale specific online drivers in Germany (BTX) and France (MTL). MTL uses YYYYMMDD format. BTX uses DD.MM.YYYY format.
Microsoft Money supports the QIF data transfer protocol developed by Intuit. Most versions of QIF have represented dates using a 2-digit year format. While the data stored in Money is Year 2000 compliant, Money needs to use a heuristic to determine the best 2-digit date to use when importing to or exporting from the QIF format. The rules of this heuristic are listed in the table below. In some versions, QIF uses an apostrophe to denote specific date ranges (for example 1/31'01). In Quicken 98, it is used to indicate the years from 1900 – 1949 and 2050 – 2099. In versions prior to Quicken 98, in Quicken 99, and in Money v. 4.0 and up, an apostrophe is used to indicate the years from 2000 – 2099. When Money98 was released, this latter interpretation of the apostrophe format was standard. Presented below is a table describing how Money interprets QIF data ranges:
| ||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
| - | ||||||||||||||||||||
| none | ||||||||||||||||||||
| Windows 95, or Windows NT 4 (no specific Service Pack is required, though Service Pack 3 is recommended) | ||||||||||||||||||||
| Operating system clock is not advanced beyond 2038 | ||||||||||||||||||||
| 08 Apr 1999 | ||||||||||||||||||||
|
Operational Range for Data: Generally January 1, 1900 – December 31, 2200 butJanuary 1, 1993 – December 31, 2092 for certain online banking Services How the product accepts dates:
Money 98 uses the OLE Automation "DATE" data type. This is represented as a double (8-byte floating point) value. The whole-number portion represents the number of days since Dec 30, 1899 A.D. The decimal portion (which Money does not use very often) represents the fraction of a day to indicate a time (e.g., 0.25=6:00am, 0.5=noon, etc.). Dates that have no time representation are stored with no decimal part. For example, January 1, 1900 would be represented as the number 2.0.
Users can enter dates in Money as a 2-digit representation (e.g., 99, 00, 01) or a 4-digit representation (e.g., 1999, 2000, 2001). Example: in the check register, the user can enter the date 1/2/00. This date is recognized as 1/2/2000. The logic that Money uses for converting 2-digit years into the actual year varies depending on what Date data entry field is in question. Money generally uses a heuristic that compares the 2-digit year that has been entered to the current year. If the Year+1900 is more than 33 years in the past, then Money assumes that the date is in the future and uses Year+2000. Dates are displayed in Microsoft Money consistent with the Windows date format setting. Years can be displayed as either 2 or 4-digit.
OFX, OFC, Visa. Money transmits date information to (and receives from) OFX, OFC and VISA using a 4-digit format (YYYYMMDD) within the operational date range for the Money product.
Checkfree: The Checkfree/ISC/NPC 4.2 specification (dated 1/23/1996) specifies the data format for communications with Checkfree. Checkfree uses six numeric digits to represent dates as YYMMDD. Money and Checkfree exchange and translate 2-digit years during Online Banking connections using the following algorithm: If YY = 00, it is considered 2000 If YY < 93, it is considered 20xx (e.g., 2092) If YY >= 93, it is considered 19xx (e.g., 1993) Applying this formula, the operational date range for Money in connection with online bill payment services with Checkfree is 1/1/1993 to 12/31/2092.
International (BTX/MTL) Money operates with two locale specific online drivers in Germany (BTX) and France (MTL). MTL uses YYYYMMDD format. BTX uses DD.MM.YYYY format.
Microsoft Money supports the QIF data transfer protocol developed by Intuit. Most versions of QIF have represented dates using a 2-digit year format. While the data stored in Money is Year 2000 compliant, Money needs to use a heuristic to determine the best 2-digit date to use when importing to or exporting from the QIF format. The rules of this heuristic are listed in the table below. In some versions, QIF uses an apostrophe to denote specific date ranges (for example 1/31'01). In Quicken 98, it is used to indicate the years from 1900 – 1949 and 2050 – 2099. In versions prior to Quicken 98, in Quicken 99, and in Money v. 4.0 and up, an apostrophe is used to indicate the years from 2000 – 2099. When Money98 was released, this latter interpretation of the apostrophe format was standard. Presented below is a table describing how Money interprets QIF data ranges:
| ||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
| - | ||||||||||||||||||||
| none | ||||||||||||||||||||
| Windows 95, or Windows NT 4 (no specific Service Pack is required, though Service Pack 3 is recommended) | ||||||||||||||||||||
| Operating system clock is not advanced beyond 2038 | ||||||||||||||||||||
| 08 Apr 1999 | ||||||||||||||||||||
|
Operational Range for Data: Generally January 1, 1900 – December 31, 2200 butJanuary 1, 1993 – December 31, 2092 for certain online banking Services How the product accepts dates:
Money 98 uses the OLE Automation "DATE" data type. This is represented as a double (8-byte floating point) value. The whole-number portion represents the number of days since Dec 30, 1899 A.D. The decimal portion (which Money does not use very often) represents the fraction of a day to indicate a time (e.g., 0.25=6:00am, 0.5=noon, etc.). Dates that have no time representation are stored with no decimal part. For example, January 1, 1900 would be represented as the number 2.0.
Users can enter dates in Money as a 2-digit representation (e.g., 99, 00, 01) or a 4-digit representation (e.g., 1999, 2000, 2001). Example: in the check register, the user can enter the date 1/2/00. This date is recognized as 1/2/2000. The logic that Money uses for converting 2-digit years into the actual year varies depending on what Date data entry field is in question. Money generally uses a heuristic that compares the 2-digit year that has been entered to the current year. If the Year+1900 is more than 33 years in the past, then Money assumes that the date is in the future and uses Year+2000. Dates are displayed in Microsoft Money consistent with the Windows date format setting. Years can be displayed as either 2 or 4-digit.
OFX, OFC, Visa. Money transmits date information to (and receives from) OFX, OFC and VISA using a 4-digit format (YYYYMMDD) within the operational date range for the Money product.
Checkfree: The Checkfree/ISC/NPC 4.2 specification (dated 1/23/1996) specifies the data format for communications with Checkfree. Checkfree uses six numeric digits to represent dates as YYMMDD. Money and Checkfree exchange and translate 2-digit years during Online Banking connections using the following algorithm: If YY = 00, it is considered 2000 If YY < 93, it is considered 20xx (e.g., 2092) If YY >= 93, it is considered 19xx (e.g., 1993) Applying this formula, the operational date range for Money in connection with online bill payment services with Checkfree is 1/1/1993 to 12/31/2092.
International (BTX/MTL) Money operates with two locale specific online drivers in Germany (BTX) and France (MTL). MTL uses YYYYMMDD format. BTX uses DD.MM.YYYY format.
Microsoft Money supports the QIF data transfer protocol developed by Intuit. Most versions of QIF have represented dates using a 2-digit year format. While the data stored in Money is Year 2000 compliant, Money needs to use a heuristic to determine the best 2-digit date to use when importing to or exporting from the QIF format. The rules of this heuristic are listed in the table below. In some versions, QIF uses an apostrophe to denote specific date ranges (for example 1/31'01). In Quicken 98, it is used to indicate the years from 1900 – 1949 and 2050 – 2099. In versions prior to Quicken 98, in Quicken 99, and in Money v. 4.0 and up, an apostrophe is used to indicate the years from 2000 – 2099. When Money98 was released, this latter interpretation of the apostrophe format was standard. Presented below is a table describing how Money interprets QIF data ranges:
| ||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
| - | ||||||||||||||||||||
| none | ||||||||||||||||||||
| Windows 95, or Windows NT 4 (no specific Service Pack is required, though Service Pack 3 is recommended) | ||||||||||||||||||||
| Operating system clock is not advanced beyond 2038 | ||||||||||||||||||||
| 08 Apr 1999 | ||||||||||||||||||||
|
Operational Range for Data: Generally January 1, 1900 – December 31, 2200 butJanuary 1, 1993 – December 31, 2092 for certain online banking Services How the product accepts dates:
Money 98 uses the OLE Automation "DATE" data type. This is represented as a double (8-byte floating point) value. The whole-number portion represents the number of days since Dec 30, 1899 A.D. The decimal portion (which Money does not use very often) represents the fraction of a day to indicate a time (e.g., 0.25=6:00am, 0.5=noon, etc.). Dates that have no time representation are stored with no decimal part. For example, January 1, 1900 would be represented as the number 2.0.
Users can enter dates in Money as a 2-digit representation (e.g., 99, 00, 01) or a 4-digit representation (e.g., 1999, 2000, 2001). Example: in the check register, the user can enter the date 1/2/00. This date is recognized as 1/2/2000. The logic that Money uses for converting 2-digit years into the actual year varies depending on what Date data entry field is in question. Money generally uses a heuristic that compares the 2-digit year that has been entered to the current year. If the Year+1900 is more than 33 years in the past, then Money assumes that the date is in the future and uses Year+2000. Dates are displayed in Microsoft Money consistent with the Windows date format setting. Years can be displayed as either 2 or 4-digit.
OFX, OFC, Visa. Money transmits date information to (and receives from) OFX, OFC and VISA using a 4-digit format (YYYYMMDD) within the operational date range for the Money product.
Checkfree: The Checkfree/ISC/NPC 4.2 specification (dated 1/23/1996) specifies the data format for communications with Checkfree. Checkfree uses six numeric digits to represent dates as YYMMDD. Money and Checkfree exchange and translate 2-digit years during Online Banking connections using the following algorithm: If YY = 00, it is considered 2000 If YY < 93, it is considered 20xx (e.g., 2092) If YY >= 93, it is considered 19xx (e.g., 1993) Applying this formula, the operational date range for Money in connection with online bill payment services with Checkfree is 1/1/1993 to 12/31/2092.
International (BTX/MTL) Money operates with two locale specific online drivers in Germany (BTX) and France (MTL). MTL uses YYYYMMDD format. BTX uses DD.MM.YYYY format.
Microsoft Money supports the QIF data transfer protocol developed by Intuit. Most versions of QIF have represented dates using a 2-digit year format. While the data stored in Money is Year 2000 compliant, Money needs to use a heuristic to determine the best 2-digit date to use when importing to or exporting from the QIF format. The rules of this heuristic are listed in the table below. In some versions, QIF uses an apostrophe to denote specific date ranges (for example 1/31'01). In Quicken 98, it is used to indicate the years from 1900 – 1949 and 2050 – 2099. In versions prior to Quicken 98, in Quicken 99, and in Money v. 4.0 and up, an apostrophe is used to indicate the years from 2000 – 2099. When Money98 was released, this latter interpretation of the apostrophe format was standard. Presented below is a table describing how Money interprets QIF data ranges:
| ||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
| 01 Jan 1900 - 31 Dec 2200 | |||
| None | |||
| Windows 9x Japanese language version, or Windows NT 4.0 SP4 or later | |||
| Operating system clock is not advanced beyond 2038 | |||
| 23 Jun 1999 | |||
| |||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
| - | ||||||||||||||||||||
| None | ||||||||||||||||||||
| Windows 95, or Windows NT 4 (no specific Service Pack is required, though Service Pack 3 is recommended) | ||||||||||||||||||||
| Operating system clock is not advanced beyond 2038 | ||||||||||||||||||||
| 08 Apr 1999 | ||||||||||||||||||||
|
Operational Range for Data: Generally January 1, 1900 – December 31, 2200 butJanuary 1, 1993 – December 31, 2092 for certain online banking Services How the product accepts dates:
Microsoft Money supports the QIF data transfer protocol developed by Intuit. Most versions of QIF have represented dates using a 2-digit year format. While the data stored in Money is Year 2000 compliant, Money needs to use a heuristic to determine the best 2-digit date to use when importing to or exporting from the QIF format. The rules of this heuristic are listed in the table below. In some versions, QIF uses an apostrophe to denote specific date ranges (for example 1/31'01). In Quicken 98, it is used to indicate the years from 1900 – 1949 and 2050 – 2099. In versions prior to Quicken 98, in Quicken 99, and in Money v. 4.0 and up, an apostrophe is used to indicate the years from 2000 – 2099. When Money98 was released, this latter interpretation of the apostrophe format was standard. Presented below is a table describing how Money interprets QIF data ranges:
| ||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
| - | ||||||||||||||||||||||||||||||||||||||
| For issue #4 only: Download mnyutil.dll update (via SmartConnect or PSS) | ||||||||||||||||||||||||||||||||||||||
| Windows 95 or later; Windows NT 4.0 or later | ||||||||||||||||||||||||||||||||||||||
| Operating system clock is not advanced beyond 2038 | ||||||||||||||||||||||||||||||||||||||
| 08 Apr 1999 | ||||||||||||||||||||||||||||||||||||||
|
Operational Range for Data: Generally January 1, 1900 – December 31, 2200.January 1, 1993 – December 31, 2092 for certain online banking services How the product accepts dates:
Money 99 uses the OLE Automation "DATE" data type. This is represented as a double (8-byte floating point) value. The whole-number portion represents the number of days since Dec 30, 1899 A.D. The decimal portion (which Money does not use very often) represents the fraction of a day to indicate a time (e.g., 0.25=6:00am, 0.5=noon, etc.). Dates that have no time representation are stored with no decimal part. For example, January 1, 1900 would be represented as the number 2.0.
Users can enter dates in Money as a 2-digit representation (e.g., 99, 00, 01) or a 4-digit representation (e.g., 1999, 2000, 2001). Example: in the check register, the user can enter the date 1/2/00. This date is recognized as 1/2/2000. The logic that Money uses for converting 2-digit years into the actual year varies depending on what Date data entry field is in question. Money generally uses a heuristic that compares the 2-digit year that has been entered to the current year. If the Year+1900 is more than 33 years in the past, then Money assumes that the date is in the future and uses Year+2000. Dates are displayed in Microsoft Money consistent with the Windows date format setting. Years can be displayed as either 2 or 4-digit. OFX, OFC, Visa. Money transmits date information to (and receives from) OFX, OFC and VISA using a 4-digit format (YYYYMMDD) within the operational date range for the Money product.
Checkfree: The Checkfree/ISC/NPC 4.2 specification (dated 1/23/1996) specifies the data format for communications with Checkfree. Checkfree uses six numeric digits to represent dates as YYMMDD. Money and Checkfree exchange and translate 2-digit years during Online Banking connections using the following algorithm: If YY = 00, it is considered 2000 If YY < 93, it is considered 20xx (e.g., 2092) If YY >= 93, it is considered 19xx (e.g., 1993) Applying this formula, the operational date range for Money in connection with online bill payment services with Checkfree is 1/1/1993 to 12/31/2092.
Microsoft Money supports the QIF data transfer protocol developed by Intuit. Most versions of QIF have represented dates using a 2-digit year format. While the data stored in Money is Year 2000 compliant, Money needs to use a heuristic to determine the best 2-digit date to use when importing to or exporting from the QIF format. The heuristic compares the 2-digit year that is being imported to the current year. If the Year+1900 is more than 33 years in the past, then Money assumes that the date is in the future and uses Year+2000. In some versions, QIF uses an apostrophe to denote specific date ranges (for example 1/31'01). In Quicken 98, it is used to indicate the years from 1900 – 1949 and 2050 – 2099. In versions prior to Quicken 98, in Quicken 99, and in Money v. 4.0 and up, an apostrophe is used to indicate the years from 2000 – 2099. It is not possible to determine which range a QIF file is using and Money currently imports these dates as blank. An available file update fixes an issue wherein transactions with a date in the apostrophe format are imported into Money99 with a blank date (since the format could mean two different date ranges as described above). Dates in the apostrophe format will now be interpreted with the same heuristic as other valid QIF date formats. The file that needs to be updated for US Money99 is mnyutil.dll version # This file is automatically updated for users who use the Update Internet Information feature in Money 99 and also available from Microsoft PSS. Presented below is a table describing how Money interprets QIF data ranges (with the mnyutil.dll update): US Money99 Basic and Financial Suite:
US Money99 P&B:
* These date ranges will change as Today’s date changes according to the heuristic Money uses. | ||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
| - | ||||||||||||||||||||||||||||||||||||||
| For issue #4 only: Download mnyutil.dll update (via SmartConnect or PSS) | ||||||||||||||||||||||||||||||||||||||
| Windows 95 or later; Windows NT 4.0 or later | ||||||||||||||||||||||||||||||||||||||
| Operating system clock is not advanced beyond 2038 | ||||||||||||||||||||||||||||||||||||||
| 13 Jul 1999 | ||||||||||||||||||||||||||||||||||||||
|
Operational Range for Data: Generally January 1, 1900 – December 31, 2200.January 1, 1993 – December 31, 2092 for certain online banking services How the product accepts dates:
Money 99 uses the OLE Automation "DATE" data type. This is represented as a double (8-byte floating point) value. The whole-number portion represents the number of days since Dec 30, 1899 A.D. The decimal portion (which Money does not use very often) represents the fraction of a day to indicate a time (e.g., 0.25=6:00am, 0.5=noon, etc.). Dates that have no time representation are stored with no decimal part. For example, January 1, 1900 would be represented as the number 2.0.
Users can enter dates in Money as a 2-digit representation (e.g., 99, 00, 01) or a 4-digit representation (e.g., 1999, 2000, 2001). Example: in the check register, the user can enter the date 1/2/00. This date is recognized as 1/2/2000. The logic that Money uses for converting 2-digit years into the actual year varies depending on what Date data entry field is in question. Money generally uses a heuristic that compares the 2-digit year that has been entered to the current year. If the Year+1900 is more than 33 years in the past, then Money assumes that the date is in the future and uses Year+2000. Dates are displayed in Microsoft Money consistent with the Windows date format setting. Years can be displayed as either 2 or 4-digit. OFX, OFC, Visa. Money transmits date information to (and receives from) OFX, OFC and VISA using a 4-digit format (YYYYMMDD) within the operational date range for the Money product.
Checkfree: The Checkfree/ISC/NPC 4.2 specification (dated 1/23/1996) specifies the data format for communications with Checkfree. Checkfree uses six numeric digits to represent dates as YYMMDD. Money and Checkfree exchange and translate 2-digit years during Online Banking connections using the following algorithm: If YY = 00, it is considered 2000 If YY < 93, it is considered 20xx (e.g., 2092) If YY >= 93, it is considered 19xx (e.g., 1993) Applying this formula, the operational date range for Money in connection with online bill payment services with Checkfree is 1/1/1993 to 12/31/2092.
The software update is available at Microsoft Money supports the QIF data transfer protocol developed by Intuit. Most versions of QIF have represented dates using a 2-digit year format. While the data stored in Money is Year 2000 compliant, Money needs to use a heuristic to determine the best 2-digit date to use when importing to or exporting from the QIF format. The heuristic compares the 2-digit year that is being imported to the current year. If the Year+1900 is more than 33 years in the past, then Money assumes that the date is in the future and uses Year+2000. In some versions, QIF uses an apostrophe to denote specific date ranges (for example 1/31'01). In Quicken 98, it is used to indicate the years from 1900 – 1949 and 2050 – 2099. In versions prior to Quicken 98, in Quicken 99, and in Money v. 4.0 and up, an apostrophe is used to indicate the years from 2000 – 2099. It is not possible to determine which range a QIF file is using and Money currently imports these dates as blank. An available file update fixes an issue wherein transactions with a date in the apostrophe format are imported into Money99 with a blank date (since the format could mean two different date ranges as described above). Dates in the apostrophe format will now be interpreted with the same heuristic as other valid QIF date formats. The file that needs to be updated for US Money99 is mnyutil.dll version # 7.00.14.2324, dated 3/24/99 2:18 pm, 495,616 bytes. This file will display as version 7.00.2324 in Windows 98 Explorer.This file is automatically updated for users who use the Update Internet Information feature in Money 99 and also available from Microsoft PSS. Presented below is a table describing how Money interprets QIF data ranges (with the mnyutil.dll update): US Money99 Basic and Financial Suite:
US Money99 P&B:
* These date ranges will change as Today’s date changes according to the heuristic Money uses. | ||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
| - | ||||||||||||||||||||||||||||||||||||||
| For issue #4 only: Download mnyutil.dll update (via SmartConnect or PSS) | ||||||||||||||||||||||||||||||||||||||
| Windows 95 or later; Windows NT 4.0 or later | ||||||||||||||||||||||||||||||||||||||
| Operating system clock is not advanced beyond 2038 | ||||||||||||||||||||||||||||||||||||||
| 08 Apr 1999 | ||||||||||||||||||||||||||||||||||||||
|
Operational Range for Data: Generally January 1, 1900 – December 31, 2200.January 1, 1993 – December 31, 2092 for certain online banking services How the product accepts dates:
Microsoft Money supports the QIF data transfer protocol developed by Intuit. Most versions of QIF have represented dates using a 2-digit year format. While the data stored in Money is Year 2000 compliant, Money needs to use a heuristic to determine the best 2-digit date to use when importing to or exporting from the QIF format. The heuristic compares the 2-digit year that is being imported to the current year. If the Year+1900 is more than 33 years in the past, then Money assumes that the date is in the future and uses Year+2000. In some versions, QIF uses an apostrophe to denote specific date ranges (for example 1/31'01). In Quicken 98, it is used to indicate the years from 1900 – 1949 and 2050 – 2099. In versions prior to Quicken 98, in Quicken 99, and in Money v. 4.0 and up, an apostrophe is used to indicate the years from 2000 – 2099. It is not possible to determine which range a QIF file is using and Money currently imports these dates as blank. An available file update fixes an issue wherein transactions with a date in the apostrophe format are imported into Money99 with a blank date (since the format could mean two different date ranges as described above). Dates in the apostrophe format will now be interpreted with the same heuristic as other valid QIF date formats. The file that needs to be updated for US Money99 is mnyutil.dll version # This file is automatically updated for users who use the Update Internet Information feature in Money 99 and also available from Microsoft PSS. Presented below is a table describing how Money interprets QIF data ranges (with the mnyutil.dll update): US Money99 Basic and Financial Suite:
US Money99 P&B:
* These date ranges will change as Today’s date changes according to the heuristic Money uses. | ||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
| - | ||||||||||||||||||||||||||||||||||||||
| For issue #4 only: Download mnyutil.dll update (via SmartConnect or PSS) | ||||||||||||||||||||||||||||||||||||||
| Windows 95 or later; Windows NT 4.0 or later | ||||||||||||||||||||||||||||||||||||||
| Operating system clock is not advanced beyond 2038 | ||||||||||||||||||||||||||||||||||||||
| 08 Apr 1999 | ||||||||||||||||||||||||||||||||||||||
|
Operational Range for Data: Generally January 1, 1900 – December 31, 2200.January 1, 1993 – December 31, 2092 for certain online banking services How the product accepts dates:
Microsoft Money supports the QIF data transfer protocol developed by Intuit. Most versions of QIF have represented dates using a 2-digit year format. While the data stored in Money is Year 2000 compliant, Money needs to use a heuristic to determine the best 2-digit date to use when importing to or exporting from the QIF format. The heuristic compares the 2-digit year that is being imported to the current year. If the Year+1900 is more than 33 years in the past, then Money assumes that the date is in the future and uses Year+2000. In some versions, QIF uses an apostrophe to denote specific date ranges (for example 1/31'01). In Quicken 98, it is used to indicate the years from 1900 – 1949 and 2050 – 2099. In versions prior to Quicken 98, in Quicken 99, and in Money v. 4.0 and up, an apostrophe is used to indicate the years from 2000 – 2099. It is not possible to determine which range a QIF file is using and Money currently imports these dates as blank. An available file update fixes an issue wherein transactions with a date in the apostrophe format are imported into Money99 with a blank date (since the format could mean two different date ranges as described above). Dates in the apostrophe format will now be interpreted with the same heuristic as other valid QIF date formats. The file that needs to be updated for US Money99 is mnyutil.dll version # This file is automatically updated for users who use the Update Internet Information feature in Money 99 and also available from Microsoft PSS. Presented below is a table describing how Money interprets QIF data ranges (with the mnyutil.dll update): US Money99 Basic and Financial Suite:
US Money99 P&B:
* These date ranges will change as Today’s date changes according to the heuristic Money uses. | ||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
| - | ||||||||||||||||||||||||||||||||||||||
| For issue #4 only: Download mnyutil.dll update (via SmartConnect or PSS) | ||||||||||||||||||||||||||||||||||||||
| Windows 95 or later; Windows NT 4.0 or later | ||||||||||||||||||||||||||||||||||||||
| Operating system clock is not advanced beyond 2038 | ||||||||||||||||||||||||||||||||||||||
| 08 Apr 1999 | ||||||||||||||||||||||||||||||||||||||
|
Operational Range for Data: Generally January 1, 1900 – December 31, 2200.January 1, 1993 – December 31, 2092 for certain online banking services How the product accepts dates:
Money 99 uses the OLE Automation "DATE" data type. This is represented as a double (8-byte floating point) value. The whole-number portion represents the number of days since Dec 30, 1899 A.D. The decimal portion (which Money does not use very often) represents the fraction of a day to indicate a time (e.g., 0.25=6:00am, 0.5=noon, etc.). Dates that have no time representation are stored with no decimal part. For example, January 1, 1900 would be represented as the number 2.0.
Users can enter dates in Money as a 2-digit representation (e.g., 99, 00, 01) or a 4-digit representation (e.g., 1999, 2000, 2001). Example: in the check register, the user can enter the date 1/2/00. This date is recognized as 1/2/2000. The logic that Money uses for converting 2-digit years into the actual year varies depending on what Date data entry field is in question. Money generally uses a heuristic that compares the 2-digit year that has been entered to the current year. If the Year+1900 is more than 33 years in the past, then Money assumes that the date is in the future and uses Year+2000. Dates are displayed in Microsoft Money consistent with the Windows date format setting. Years can be displayed as either 2 or 4-digit. OFX, OFC, Visa. Money transmits date information to (and receives from) OFX, OFC and VISA using a 4-digit format (YYYYMMDD) within the operational date range for the Money product.
Checkfree: The Checkfree/ISC/NPC 4.2 specification (dated 1/23/1996) specifies the data format for communications with Checkfree. Checkfree uses six numeric digits to represent dates as YYMMDD. Money and Checkfree exchange and translate 2-digit years during Online Banking connections using the following algorithm: If YY = 00, it is considered 2000 If YY < 93, it is considered 20xx (e.g., 2092) If YY >= 93, it is considered 19xx (e.g., 1993) Applying this formula, the operational date range for Money in connection with online bill payment services with Checkfree is 1/1/1993 to 12/31/2092.
Microsoft Money supports the QIF data transfer protocol developed by Intuit. Most versions of QIF have represented dates using a 2-digit year format. While the data stored in Money is Year 2000 compliant, Money needs to use a heuristic to determine the best 2-digit date to use when importing to or exporting from the QIF format. The heuristic compares the 2-digit year that is being imported to the current year. If the Year+1900 is more than 33 years in the past, then Money assumes that the date is in the future and uses Year+2000. In some versions, QIF uses an apostrophe to denote specific date ranges (for example 1/31'01). In Quicken 98, it is used to indicate the years from 1900 – 1949 and 2050 – 2099. In versions prior to Quicken 98, in Quicken 99, and in Money v. 4.0 and up, an apostrophe is used to indicate the years from 2000 – 2099. It is not possible to determine which range a QIF file is using and Money currently imports these dates as blank. An available file update fixes an issue wherein transactions with a date in the apostrophe format are imported into Money99 with a blank date (since the format could mean two different date ranges as described above). Dates in the apostrophe format will now be interpreted with the same heuristic as other valid QIF date formats. The file that needs to be updated for US Money99 is mnyutil.dll version # This file is automatically updated for users who use the Update Internet Information feature in Money 99 and also available from Microsoft PSS. Presented below is a table describing how Money interprets QIF data ranges (with the mnyutil.dll update): US Money99 Basic and Financial Suite:
US Money99 P&B:
* These date ranges will change as Today’s date changes according to the heuristic Money uses. | ||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
| - | ||||||||||||||||||||||||||||||||||||||
| For issue #4 only: Download mnyutil.dll update (via SmartConnect or PSS) | ||||||||||||||||||||||||||||||||||||||
| Windows 95 or later; Windows NT 4.0 or later | ||||||||||||||||||||||||||||||||||||||
| Operating system clock is not advanced beyond 2038 | ||||||||||||||||||||||||||||||||||||||
| 08 Apr 1999 | ||||||||||||||||||||||||||||||||||||||
|
Operational Range for Data: Generally January 1, 1900 – December 31, 2200.January 1, 1993 – December 31, 2092 for certain online banking services How the product accepts dates:
Money 99 uses the OLE Automation "DATE" data type. This is represented as a double (8-byte floating point) value. The whole-number portion represents the number of days since Dec 30, 1899 A.D. The decimal portion (which Money does not use very often) represents the fraction of a day to indicate a time (e.g., 0.25=6:00am, 0.5=noon, etc.). Dates that have no time representation are stored with no decimal part. For example, January 1, 1900 would be represented as the number 2.0.
Users can enter dates in Money as a 2-digit representation (e.g., 99, 00, 01) or a 4-digit representation (e.g., 1999, 2000, 2001). Example: in the check register, the user can enter the date 1/2/00. This date is recognized as 1/2/2000. The logic that Money uses for converting 2-digit years into the actual year varies depending on what Date data entry field is in question. Money generally uses a heuristic that compares the 2-digit year that has been entered to the current year. If the Year+1900 is more than 33 years in the past, then Money assumes that the date is in the future and uses Year+2000. Dates are displayed in Microsoft Money consistent with the Windows date format setting. Years can be displayed as either 2 or 4-digit. OFX, OFC, Visa. Money transmits date information to (and receives from) OFX, OFC and VISA using a 4-digit format (YYYYMMDD) within the operational date range for the Money product.
Checkfree: The Checkfree/ISC/NPC 4.2 specification (dated 1/23/1996) specifies the data format for communications with Checkfree. Checkfree uses six numeric digits to represent dates as YYMMDD. Money and Checkfree exchange and translate 2-digit years during Online Banking connections using the following algorithm: If YY = 00, it is considered 2000 If YY < 93, it is considered 20xx (e.g., 2092) If YY >= 93, it is considered 19xx (e.g., 1993) Applying this formula, the operational date range for Money in connection with online bill payment services with Checkfree is 1/1/1993 to 12/31/2092.
Microsoft Money supports the QIF data transfer protocol developed by Intuit. Most versions of QIF have represented dates using a 2-digit year format. While the data stored in Money is Year 2000 compliant, Money needs to use a heuristic to determine the best 2-digit date to use when importing to or exporting from the QIF format. The heuristic compares the 2-digit year that is being imported to the current year. If the Year+1900 is more than 33 years in the past, then Money assumes that the date is in the future and uses Year+2000. In some versions, QIF uses an apostrophe to denote specific date ranges (for example 1/31'01). In Quicken 98, it is used to indicate the years from 1900 – 1949 and 2050 – 2099. In versions prior to Quicken 98, in Quicken 99, and in Money v. 4.0 and up, an apostrophe is used to indicate the years from 2000 – 2099. It is not possible to determine which range a QIF file is using and Money currently imports these dates as blank. An available file update fixes an issue wherein transactions with a date in the apostrophe format are imported into Money99 with a blank date (since the format could mean two different date ranges as described above). Dates in the apostrophe format will now be interpreted with the same heuristic as other valid QIF date formats. The file that needs to be updated for US Money99 is mnyutil.dll version # This file is automatically updated for users who use the Update Internet Information feature in Money 99 and also available from Microsoft PSS. Presented below is a table describing how Money interprets QIF data ranges (with the mnyutil.dll update): US Money99 Basic and Financial Suite:
US Money99 P&B:
* These date ranges will change as Today’s date changes according to the heuristic Money uses. | ||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
| - | ||||||||||||||||||||||||||||||||||||||
| For issue #4 only: Download mnyutil.dll update (via SmartConnect or PSS) | ||||||||||||||||||||||||||||||||||||||
| Windows 95 or later; Windows NT 4.0 or later | ||||||||||||||||||||||||||||||||||||||
| Operating system clock is not advanced beyond 2038 | ||||||||||||||||||||||||||||||||||||||
| 08 Apr 1999 | ||||||||||||||||||||||||||||||||||||||
|
Operational Range for Data: Generally January 1, 1900 – December 31, 2200.January 1, 1993 – December 31, 2092 for certain online banking services How the product accepts dates:
Money 99 uses the OLE Automation "DATE" data type. This is represented as a double (8-byte floating point) value. The whole-number portion represents the number of days since Dec 30, 1899 A.D. The decimal portion (which Money does not use very often) represents the fraction of a day to indicate a time (e.g., 0.25=6:00am, 0.5=noon, etc.). Dates that have no time representation are stored with no decimal part. For example, January 1, 1900 would be represented as the number 2.0.
Users can enter dates in Money as a 2-digit representation (e.g., 99, 00, 01) or a 4-digit representation (e.g., 1999, 2000, 2001). Example: in the check register, the user can enter the date 1/2/00. This date is recognized as 1/2/2000. The logic that Money uses for converting 2-digit years into the actual year varies depending on what Date data entry field is in question. Money generally uses a heuristic that compares the 2-digit year that has been entered to the current year. If the Year+1900 is more than 33 years in the past, then Money assumes that the date is in the future and uses Year+2000. Dates are displayed in Microsoft Money consistent with the Windows date format setting. Years can be displayed as either 2 or 4-digit. OFX, OFC, Visa. Money transmits date information to (and receives from) OFX, OFC and VISA using a 4-digit format (YYYYMMDD) within the operational date range for the Money product.
Checkfree: The Checkfree/ISC/NPC 4.2 specification (dated 1/23/1996) specifies the data format for communications with Checkfree. Checkfree uses six numeric digits to represent dates as YYMMDD. Money and Checkfree exchange and translate 2-digit years during Online Banking connections using the following algorithm: If YY = 00, it is considered 2000 If YY < 93, it is considered 20xx (e.g., 2092) If YY >= 93, it is considered 19xx (e.g., 1993) Applying this formula, the operational date range for Money in connection with online bill payment services with Checkfree is 1/1/1993 to 12/31/2092.
Microsoft Money supports the QIF data transfer protocol developed by Intuit. Most versions of QIF have represented dates using a 2-digit year format. While the data stored in Money is Year 2000 compliant, Money needs to use a heuristic to determine the best 2-digit date to use when importing to or exporting from the QIF format. The heuristic compares the 2-digit year that is being imported to the current year. If the Year+1900 is more than 33 years in the past, then Money assumes that the date is in the future and uses Year+2000. In some versions, QIF uses an apostrophe to denote specific date ranges (for example 1/31'01). In Quicken 98, it is used to indicate the years from 1900 – 1949 and 2050 – 2099. In versions prior to Quicken 98, in Quicken 99, and in Money v. 4.0 and up, an apostrophe is used to indicate the years from 2000 – 2099. It is not possible to determine which range a QIF file is using and Money currently imports these dates as blank. An available file update fixes an issue wherein transactions with a date in the apostrophe format are imported into Money99 with a blank date (since the format could mean two different date ranges as described above). Dates in the apostrophe format will now be interpreted with the same heuristic as other valid QIF date formats. The file that needs to be updated for US Money99 is mnyutil.dll version # This file is automatically updated for users who use the Update Internet Information feature in Money 99 and also available from Microsoft PSS. Presented below is a table describing how Money interprets QIF data ranges (with the mnyutil.dll update): US Money99 Basic and Financial Suite:
US Money99 P&B:
* These date ranges will change as Today’s date changes according to the heuristic Money uses. | ||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
| - | |||||||||||||||||||||||||||||||||||
| For issue #4 only: Download mnyutil.dll update (via SmartConnect or PSS) | |||||||||||||||||||||||||||||||||||
| Windows 95 or later; Windows NT 4.0 or later | |||||||||||||||||||||||||||||||||||
| Operating system clock is not advanced beyond 2038 | |||||||||||||||||||||||||||||||||||
| 08 Apr 1999 | |||||||||||||||||||||||||||||||||||
|
Operational Range for Data: Generally January 1, 1900 – December 31, 2200.January 1, 1993 – December 31, 2092 for certain online banking services How the product accepts dates:
Microsoft Money supports the QIF data transfer protocol developed by Intuit. Most versions of QIF have represented dates using a 2-digit year format. While the data stored in Money is Year 2000 compliant, Money needs to use a heuristic to determine the best 2-digit date to use when importing to or exporting from the QIF format. The heuristic compares the 2-digit year that is being imported to the current year. If the Year+1900 is more than 33 years in the past, then Money assumes that the date is in the future and uses Year+2000. In some versions, QIF uses an apostrophe to denote specific date ranges (for example 1/31'01). In Quicken 98, it is used to indicate the years from 1900 – 1949 and 2050 – 2099. In versions prior to Quicken 98, in Quicken 99, and in Money v. 4.0 and up, an apostrophe is used to indicate the years from 2000 – 2099. It is not possible to determine which range a QIF file is using and Money currently imports these dates as blank. An available file update fixes an issue wherein transactions with a date in the apostrophe format are imported into Money99 with a blank date (since the format could mean two different date ranges as described above). Dates in the apostrophe format will now be interpreted with the same heuristic as other valid QIF date formats. The file that needs to be updated for US Money99 is mnyutil.dll version # This file is automatically updated for users who use the Update Internet Information feature in Money 99 and also available from Microsoft PSS. Presented below is a table describing how Money interprets QIF data ranges (with the mnyutil.dll update): US Money99 Basic and Financial Suite:
US Money99 P&B:
| |||||||||||||||||||||||||||||||||||