Import Errors - Errors.log

The following are error messages which may appear in the errors<n>.log file produced during an import into Intersection Magic. Most of these errors result in data being changed during the import process. Usually a value which is out of range is changed to a zero and then imported. In all but two cases, the record will be imported anyway.

The message "[ln] record not added: msg chars 1-20 (sample data)" indicates that the record was not written to disk. This should only occur after an indication that the caseid or date were invalid.

The other situation when a record will not be imported occurs when the database manager can not add the record to the database. This is rare and is usually preceded by warnings about low disk space.

Importer Errors:	Description
[ln:fn] <msg> For: CaseId	This message is generated once for each field which has an error. Many of these errors may occur for each record. ln: The line number of the record in the ASCII file. fn: The field name which had an error. CaseId: The CaseId of the record in question. Msg: The reason this field could not be imported.
[ln:uf] ( CaseId ) Number to great <nn>	The specified user field had a value greater than what a user field can accommodate. The value was set to 0. uf: The field number (within IMW) which had an error.
[ln:uf] <Msg> For: CaseId	This message is generated once for each field which has an error. Many of these errors may occur for each record.
[ln] BLANK LINE FOUND IN DATA FILE	The data file contained a blank line. It was ignored.
[ln] FAILED READ LINE	An unknown file i/o error occured. This usually means that the file was not a proper ASCII file.
[ln] Msg	An general error occured as described in the message.
[ln] RECORD NOT ADDED: Msg CHARS 1-20 (Sampledata)	This record could not be added to the database. Message describes why, Sample data contains the first 20 characters in the record.

[ln] User warned, disk space down to: xx	Disk space was low and a message box was presented to the user indicating that. The user continued anyway.
ASCII delimited field (n) does not exist Older version: No data at: dfn sp ct xxx~yyy~zzz	The import definition specifies a field number which is greater than the number of fields in this record. The record will be imported, this field will be blank. This should rarely occur. Old version: The old version of this message indicates means the same thing, but reports different information: dfn: delimited field number sp: start position in field ct: number of characters xxx: data in first field of record yyy: data in second field of record zzz: data in third field of record
ASCII fixed field position (n) is beyond the record Older version: No data at: dfn sp ct	The import definition specifies a character position which is greater than the number of characters in this record. The record will be imported, this field will be blank. This is common in situations where the last fields in a record indicate optional information such as vehicle three data.
Couldn't load supp import: msg	An .IMS file was not available, or memory was too low to load it.
FAILED TO BEGIN IMPORT: <msg>	The database manager was unable to prepare the database for importing.
FAILED TO RESET IMPORT FILE: <DelFileName>	The source data file could not be opened. This generally means that the file was not accessible due to security.
FAILED TO SKIP TO VALID CHAR	The program could not find valid data to begin importing.
Insufficient memory for import buffer	Memory was too low.
Replacing record	The CaseId being imported already exists in the database. The program will delete that record and add a new one from this import. Note that the CaseId may have been added during this very import, earlier on.
Supplementing data	The CaseId being imported already exists in the database. The user has checked the box in the import dialog which tells the program not to erase the original record, but rather to fill in any valid fields from this second import.