![](/file/18315/Y2K_Resource_Nov99.iso/webcon~1/usa/year2k/images/spacer.gif)
Microsoft Year 2000 Readiness Disclosure & Resource Center |
![](/file/18315/Y2K_Resource_Nov99.iso/webcon~1/usa/year2k/images/spacer.gif) |
![](/file/18315/Y2K_Resource_Nov99.iso/webcon~1/usa/year2k/images/spacer.gif) |
![](/file/18315/Y2K_Resource_Nov99.iso/webcon~1/usa/year2k/images/spacer.gif) | Money 99 (Latin America) - 32-Bit Win
Product Summary |
Product: Money Version: 99 |
Category: Compliant* Operating System: 32-Bit Win |
Language: Latin America |
Release Date: 29 Jul 1998 |
Operational Range: |
- |
Prerequisites: |
For issue #4 only: Download mnyutil.dll update (via SmartConnect or PSS) |
Product Dependencies: |
Windows 95 or later; Windows NT 4.0 or later |
Clock Dependencies: |
Operating system clock is not advanced beyond 2038 |
Last Updated: |
08 Apr 1999 | |
Product Details |
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:
- Four-Digit 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.
- Two Digit Dates.
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.
- Online Banking Services.
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.
- Money Support for QIF Protocol.
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:
Transaction Dates in Money |
Exported to QIF as |
1/1/1900-12/31/1999 |
M/D/YY |
1/1/2000-12/31/2099 |
M/DÆYY |
1/1/2100 û 12/31/2200 |
M/DÆYY |
QIF Dates |
Imported into Money as |
MM/DD/YY
1/1/00 û 12/31/99 |
1/1/1966 û 12/31/2065* |
MM/DDÆYY
1/1Æ00 û 12/31Æ99 |
1/1/1966 û 12/31/2065* |
Invalid Date |
Blank Date |
MM/DD/YYYY or
MM/DDÆYYYY |
1/1/1900 û 12/31/2200 |
US Money99 P&B:
Transaction Dates in Money |
Exported to QIF as |
1/1/1900-12/31/1999 |
M/D/YY |
1/1/2000-12/31/2099 |
M/DÆYY |
1/1/2100 û 12/31/2200 |
M/DÆYY |
QIF Dates |
Imported into Money as |
MM/DD/YY
1/1/00 û 12/31/99 |
1/1/1966-12/31/2065* |
MM/DDÆYY
1/1Æ00 û 12/31Æ99 |
1/1/1966-12/31/2065* |
Invalid Date |
Blank Date |
MM/DD/YYYY or
MM/DDÆYYYY |
1/1/1900 û 12/31/2200 |
* These date ranges will change as TodayÆs date changes according to the heuristic Money uses. | |
Return to Search Screen
Legend of Symbols: |
* |
The product is compliant with recommended customer action. This indicates a prerequisite action is recommended which may include loading a software update or reading a document. |
# |
The product is compliant with an acceptable deviations 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 with pending Year 2000 software updates. Future maintenance actions will be recommended shortly. See Product Guide for further details. |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
If after reviewing this information you have additional questions related to this product, click here.
YEAR 2000 READINESS DISCLOSURE
ALL COMMUNICATIONS OR CONVEYANCES OF INFORMATION TO YOU CONCERNING MICROSOFT AND THE YEAR 2000, INCLUDING BUT NOT LIMITED TO THIS DOCUMENT OR ANY OTHER PAST, PRESENT OR FUTURE INFORMATION REGARDING YEAR 2000 TESTING, ASSESSMENTS, READINESS, TIME TABLES, OBJECTIVES, OR OTHER (COLLECTIVELY THE "MICROSOFT YEAR 2000 STATEMENT"), ARE PROVIDED AS A "YEAR 2000 READINESS DISCLOSURE" (AS DEFINED BY THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT) AND CAN BE FOUND AT MICROSOFT'S YEAR 2000 WEBSITE LOCATED AT http://www.microsoft.com/year2000/ (the "Y2K WEBSITE"). EACH MICROSOFT YEAR 2000 STATEMENT IS PROVIDED PURSUANT TO THE TERMS HEREOF, THE TERMS OF THE Y2K WEBSITE, AND THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT FOR THE SOLE PURPOSE OF ASSISTING THE PLANNING FOR THE TRANSITION TO THE YEAR 2000. EACH MICROSOFT YEAR 2000 STATEMENT CONTAINS INFORMATION CURRENTLY AVAILABLE AND IS UPDATED REGULARLY AND SUBJECT TO CHANGE. MICROSOFT THEREFORE RECOMMENDS THAT YOU CHECK THE Y2K WEBSITE REGULARLY FOR ANY CHANGES TO ANY MICROSOFT YEAR 2000 STATEMENT. EACH MICROSOFT YEAR 2000 STATEMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. CONSEQUENTLY, MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. MOREOVER, MICROSOFT DOES NOT WARRANT OR MAKE ANY REPRESENTATIONS REGARDING THE USE OR THE RESULTS OF THE USE OF ANY MICROSOFT YEAR 2000 STATEMENT IN TERMS OF ITS CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE. NO ORAL OR WRITTEN INFORMATION OR ADVICE GIVEN BY MICROSOFT OR ITS AUTHORIZED REPRESENTATIVES SHALL CREATE A WARRANTY OR IN ANY WAY DECREASE THE SCOPE OF THIS WARRANTY DISCLAIMER. IN NO EVENT SHALL MICROSOFT OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER REGARDING ANY MICROSOFT YEAR 2000 STATEMENT INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS, PUNITIVE OR SPECIAL DAMAGES, EVEN IF MICROSOFT OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, SO THE FOREGOING LIMITATION MAY NOT APPLY TO YOU. THE INFORMATION CONTAINED IN EACH MICROSOFT YEAR 2000 STATEMENT IS FOUND AT THE Y2K WEBSITE AND IS INTENDED TO BE READ IN CONJUNCTION WITH OTHER INFORMATION LOCATED AT THE Y2K WEBSITE, INCLUDING BUT NOT LIMITED TO MICROSOFT'S YEAR 2000 COMPLIANCE STATEMENT, THE DESCRIPTION OF THE CATEGORIES OF COMPLIANCE INTO WHICH MICROSOFT HAS CLASSIFIED ITS PRODUCTS IN ITS YEAR 2000 PRODUCT GUIDE, AND THE MICROSOFT YEAR 2000 TEST CRITERIA.
ANY MICROSOFT YEAR 2000 STATEMENTS MADE TO YOU IN THE COURSE OF PROVIDING YEAR 2000 RELATED UPDATES, YEAR 2000 DIAGNOSTIC TOOLS, OR REMEDIATION SERVICES (IF ANY) ARE SUBJECT TO THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT (112 STAT. 2386). IN CASE OF A DISPUTE, THIS ACT MAY REDUCE YOUR LEGAL RIGHTS REGARDING THE USE OF ANY SUCH STATEMENTS, UNLESS OTHERWISE SPECIFIED BY YOUR CONTRACT OR TARIFF.
|