IMWEdit with IMW version 6.52x - Upon opening IMWEdit or loading a database in IMWEdit, the program reports that it can not intialize the database, and then proceeds to open with no active database.
Intersection Magic version 22.214.171.124 introduced new functionality to protect your data from incorrect entries in your streets changes file. The program will not process your street changes file when a problem is detected.
Due to a bug in the program, the reindex process, when combined with data entry, change streets, or remove unused streets, can cause street names to become renumbered. This can cause the relationships with crash records to break.
After opening Intersection Magic users may find that the database selected during their previous use of the program is no longer selected, and the new diagram button is grayed out.
Bad dates inadvertently get entered into an Intersection Magic database and can not be recognized by the program. IMW can not do a search of a 00/00/0000 date, because the date is invalid ("bad date").
Making the Address or Mile Post fields blank in IMW Edit will store invalid numeric values in the database for those fields, and can cause program crashes.
Some users have created or modified their own configurations, and now have concerns or problems with them.
Intersection Magic does not support long file names. IMW takes advantage of MS Windows to convert long names, to short names. The resulting names have a tilde (~) as the second to last character.
Under this version of Novell client, when running Windows NT/2000/XP, IMW fails to open the database. Instead it reports a File I/O error.
The Canon N1000 printer driver raises this error when printing graphics from Intersection Magic. After closing the dialog box, Intersection Magic closes without printing or further warning.
When running Windows NT/2000/XP, IMW fails to open the database. Instead it reports a File I/O error.
When Intersection Magic has an error or crashes, it often provides a numeric error code. This article lists the numeric and associated text error messages.
IMW is crashing when trying to generate a sliding spot report.
If there is a conflict between Intersection Magic and another software program on your computer, it can be helpful to identify the environment that your system is running in. Rather than ask you question after question, there are some tools that ship with Windows that can help. This article lists some of them.
User receives an error message stating trial period has expired or no active database when using the IMW Editor.
Intersection Magic keeps track of users who are accessing the database. At any one time there may be many people READING from the database. However, if anyone is writing to the database, no one else may READ or WRITE at the same time. If you are attempting to READ when you get this message, then another use has opened the database for WRITING. If you attempting to WRITE to the database, then another user is READING the database. Note: This message can also be caused by the program having crashed during a READ or WRITE operation and not released its lock on the database.
Unable to print to any printer in IMW (specifically an HP1220C). Able to print using other applications.
For one user installation, the program crashes when trying to print to a color printer. The user is running Windows 98 using the driver for Xerox Phaser 2135 v4.
In some cases street names appear twice in cross streets listings and that it can cause confusion when selecting street names.
The © and ¨ symbols are placeholders for a carriage return. While these symbols are generally hidden from view, they are visible in files, and in some edit controls.
This problem occurs when your printer is set to a resolution higher than 300dpi. Intersection Magic is still printing to some internal coordinates that reflect 300dpi.
When printing an accident list, the printer reports that it has insufficient memory. Repeated clicks to close the dialog result in partial output.
This version contained a small piece of code that causes the message "Can't load 16-bit Windows application" to be presented when the program tries to load.
The text: Record Scan Canceled is displayed when creating a diagram or running a report. After dismissing the dialog several times, it goes away.
Some viewers, under some versions of windows return a code that Intersection Magic is not expecting. As a result, after properly loading the program, Intersection Magic crashes.
Certain fast computers crash when the user closes a diagram.
When there are greater than 16,000 accidents to be generated on an all-data diagram, the program may crash.
Under certain circumstances, especially when an Intersection Magic program directory is copied from one computer to another, many settings come along with it that may confuse Windows or Intersection Magic. The result is that the program may not permit printing, changing printers, or configuring printers.
Whenever Pd' Programming changes the Intersection Magic database structure, the program automatically "knows" to update the database and its indexes. In a couple of situations, the program prompts the user to update the indexes and then doesn't seem satisfied, requiring it over and over again.
The data entry program, imwedit.exe, responds incorrectly in certain circumstances when there are no crashes in the database.
When in the data entry program - imwedit.exe, the computer beeps when enter or tab is pressed rather than moving from field to field as intended.
In one user installation, the program crashes when closing the last collision diagram on the screen. The only known specifics are: The user is running Window 95 on an HP Vectra 166/32. Norton Antivirus is in background.
A very long street name exists in the database, but diagrams for locations on that street can not be generated, and sometimes the street itself is missing from high accident location lists.
After upgrading to v6.002 from an earlier version, the message "Failed to init object tables (TBS/TAB)" appears on the first query request. Further processes do not function.
The error "Number too great" is logged when a value being imported into a user-field is greater than the max allowed value of 254.