This article explains the BACKTRACK error message "The resultant quantity will exceed the maximum length that has been setup for the quantity field." and details how to fix the underlying problem that caused it to appear.

BACKTRACK has encountered records with duplicate key field values.  This has been seen with the GROUP, RELATION, and ITEM tables.  In some cases, BACKTRACK will...

BACKTRACK requires each item to have a location. Without one on the import file, BACKTRACK cannot import it without assigning a location.

This error occurs when BACKTRACK is trying to open a report that was created in a previous version.  BACKTRACK went through a major change when version 2012 was...

This error occurred when trying to assign a new auto-assign value to User ID that exceeded the limit of the field length set for the User ID field.

This error generally occurs during a conversion or upgrade of software version in BACKTRACK.  It points to a situation which the program ran out of memory (RAM) during ...

During the customization of BACKTRACK, user can specify external table (DBF file) as source for data entry and/or validation.  This error occurs when the system cannot find...

The number auto-generated for User ID exceeded the length of the field, BACKTRACK considers a User ID value greater than the User ID field length to be 'negative'.

This appears to be a generic error message indicating that the BACKTRACK application code has failed to execute a command. We have seen this appear in the following...

This is a generic ".Net" error message (called the "Check Engine Light" message). It often refers to a problem with the software coding where there is an issue with an object...

BACKTRACK is unable to open a database. This often happens when trying to open BACKTRACK after a troubled restore.

The restore in BACKTRACK had to stop abruptly due to 'System.OutOfMemoryException'.

This error occurred as result of improper configuration of trigger in the TRANS table in a SQL database.  It resulted in the execution of an update statement before the record is...

There are no items/transactions in the BACKTRACK application you are attempting to archive.

BACKTRACK installer is unable to close some files during an install or uninstall process.  It indicates that there are applications that use some of the components BACKTRACK...

As a relational database, BACKTRACK routinely updates, add, and remotes records from the various tables that comprise the database structure. Each table requires a field or ...

When uploading information from the PDT into a PC running BACKTRACK, the PDT data is stored in a temporary location in the BACKTRACK database.  After the upload is...

BACKTRACK was unable to delete the "strings" database where template information for BACKTRACK is kept. This occurred when trying to uninstall and reinstall ...

This error occurs when BACKTRACK is trying to program a PDT with a BACKTRACK application that uses fields with Relations to external DBF files. If the DBF files are ...

This is a generic .Net programming error message indicating that whatever BACKTRACK tried to 'invoke' threw an error. ...

A client workstation could not run BACKTRACK after the program delivered a message, "Failed to get license information.  No connection could be made because the target machine actively refused it..." This article explains the situation and the solution.

This message indicates that the license for BACKTRACK, LABELVIEW, or CODESOFT has been invalidated resulting in the software being unable to function. A Hardware ...

This error message seems to indicate that the data that BACKTRACK is working with at the time not match the rules for the data in the particular database field. For example ...

When performing a add/move/delete to a record on BACKTRACK, the error message: "Item Column: Must have non-unique records" appears. ...

BACKTRACK is unable to create a new database during install. There could be multiple causes of this. In this case, it appears the version of SQL (i.e. 2008) had a conflict ...

The most likely cause for this error is that the PDT is not properly setup to communicate with the computer. Windows Mobile Device Center is at the center of this issue. ...

This article explains the BACKTRACK error message "Resource file already in use" and details how to fix the underlying problem that caused it to appear.

This error message indicates that there is a problem with BACKTRACK accessing the database table: USER.USER_NAME. This is a common SQL error message ...

BACKTRACK is unable to access files on local BT6 directory (the directory on the Client PC). This is likely because the user logged into the workstation does not have ...

There is another application that is accessing the same database that you are attempting to connect to with BACKTRACK. The connection that the other application has with ...

There is a communication problem between client workstation (BACKTRACK) and SQL server the system where the data for BACKTRACK is stored. An incorrect ...

BACKTRACK workstation is unable to locate the license information required to run the software. This is generally applied to the network installation of BACKTRACK and not ...

There was a misconfigured item in the ITEM table. In this case, BACKTRACK is being used for item tracking. No parent item involvement. However, some of the items were ...

BACKTRACK checks to make sure the data received from a PDT (i.e. upload) comes from a PDT program that was downloaded by the same BACKTRACK and that the ...

There is a communication problem between client workstation (BACKTRACK) and SQL server the system where the data for BACKTRACK is stored.  There are several...

There is a communication problem between client workstation (BACKTRACK) and SQL server the system where the data for BACKTRACK is stored. In most instance, that ...

This is often due to BACKTRACK executing a long and/or resource consuming task. Typically, waiting is what is required. ...

We investigated and confirmed the problem. It is a software defect. It is a known and documented issue. This has been reported to TEKLYNX and they will have to...

BACKTRACK versions up to and including 6 were able to use FoxPro as the database. As a relational database without a server component, FoxPro did need...

n network environment, BACKTRACK client cannot start the software. The system has 5 user licenses and only one or two users are online ...

User is unable to create a new label after deleting the sample label in BACKTRACK 2012. If the sample label is deleted before any labels have been first created, the system will produce an error message...

When trying to print or edit label from BACKTRACK, CODESOFT will open, the label will briefly appear on the CODESOFT screen then CODESOFT will exit. ...

This message is from Microsoft .NET platform. Te problem is isolated to the Teklynx patch dated 05/06/15 which brings the version to 2012.0.5.138...

Two known ways to get data out of BACKTRACK: export using BACKTRACK Export features, or query using SQL Management Studio ...

Potential reasons include: fields in the label are not properly mapped to the BACKTRACK fields, or fields in label are not formatted correctly...

When creating a new record (such as a new item), BACKTRACK inserts a new record into an item table. The record inserted must have a unique key field and fields set as 'required' must be completed...

To resolve the issue, the user needs to import transaction type using the transaction import function on BACKTRACK...

The BTWForm.ini file keeps the location settings for the BACKTRACK screens. Sometimes the tool bar can be moved into a position where it is not visible on ...

The import process in BACKTRACK for Transaction records is different from other imports. For other imports, BACKTRACK simply adds the new records (or updates ...

The label does not have the proper fields configured to allow for data mapping. A common problem is to use the wrong Data Source type...