Crash Magic Online
  Intersection Magic
  Map Magic
  Knowledge Base
  Contact Us


IMW in the year 2000 

Registration keys moved to client area: Select login on the left menu bar.

Product information Comparison matrix Support Downloads (& demos)

Will Intersection Magic continue to function correctly after Dec 31, 1999?

Click here for a "Corporate Legal Statement"

Yes, Every version of Intersection Magic ever shipped stores all of its dates as julian numbers. This means that we shouldn't have any date problems for as long as cars skid on pavement. However, your source data may not be year 2000 compatible.

Also, the dialog boxes which prompt the user for a date provide the convenience of accepting two-digit years. This means that you can enter 1/1/97 and expect that it will be recognized as 1/1/1997. This feature will fail in the year 2000. It will assume that 1/1/00 is 1/1/1900. However, if you enter a full year such as 1/1/2000, there will be no problems. Versions of Intersection Magic after v5.6 (October, 1998) will actually make a fair guess regarding the century that you intended. In these versions, 1/1/46 - 1/1/99 will be assumed to be in the 1900's. 1/1/00 through 1/1/45 will be assumed to be in the 2000's. This minor enhancement is the only change being made to the Intersection Magic date management engine.

How can I tell if my source data will continue to work past Dec 31, 1999?

Make sure that the data you are importing contains the century as well as the year. If it contains the century, you'll have no problems from Intersection Magic. The best ways to format your dates are: mm/dd/yyyy or yyyymmdd. However, we support many other formats.

What if I'm entering data manually using IMWEdit, Intersection Magic's data entry program?

IMWEdit uses the same routines as Intersection Magic. All dates have the century 1900 added automatically during entry. Again, beginning with v5.6, an attempt is made to determine the intended century if none is given.

What if my data doesn't contain the century?

You've got three choices:

  1. The best option is to add the century to your source data. In most cases, this will require a minor change in your import definition. The manual describes how to change your import definition.
  2. Another option is to modify your import definition to add the century during the import process. this will simply result in a '19' or '20' being added to the year during the import process.
  3. The final option is to upgrade to Intersection Magic v5.516 (April 1998). This option will automatically fix dates which are in the following formats:
    1. mm/dd/yy
    2. yy/mm/dd
    3. mmddyy
    4. yymmdd
    5. mm/dd/xxyy (where xx is in place but is invalid)

This version of the program will automatically put the date in the correct century based on the following rule: Any dates where the year is before '45 will be considered to be in the 21st century. Any dates where the year is after '45 will be considered to be in the 20th century. (i.e. 01/01/98 = 01/01/1998 and 01/01/00 = 01/01/2000 and 01/01/30 = 01/01/2030) The century and split year (45) are configurable so it ought'a work for the next several hundred years.

IMPORTANT information on updating your configuration

Whether you update your configuration yourself, or download a new one, or even if you have us prepare a new one for you... You must syncronize its first use with the first year 2000 compatible data which you import.

If you were to use your existing configuration to import dates which all of a sudden are two characters longer, you would get inaccurate data. In the same way, if you were to use an updated configuration on older data which didn't have the century, you would get inaccurate data as well. The configuration being used must match the data being imported.

Help for specific situations

July 26, 2017 4:32AM

© 1999-2017 Pd' Programming, Inc - Lafayette, CO USA