407-248-1481

QuoteWerks Knowledgebase Topic (Article ID 6451)

Database - Run-time error '9': Subscript out of range

This information applies to :

Article ID
6451

Created/Updated
August 27, 2015

Category
Support


Are you using the most current release of QuoteWerks?
Version 24.0 Build 2
Issue:

You are receiving the following error upon attempting to convert to order / invoice, etc. This issue might also appear when starting QuoteWerks.

Run-time error 9: Subscript out of range

Cause 1:

The logged in user's ini file has become corrupt.

Cause 2:

The system database has been tampered with; e.g. adding extra fields to a database (Headers, Items, or Products).

Solution 1:

1) Have the user close QuoteWerks
2) Find the user's ini file in the main QuoteWerks folder and rename it.
3) Reopen QuoteWerks and the issue should be gone.


Note: Each user has their own .ini file in the root of the QuoteWerks directory. For example, if the Salesrep username is John Doe, you may find an .ini file in the QuoteWerks directory named JohnD.ini.

To find the name of the user's .ini file name, select the Utilities->User Maintenance menu, highlight a user and press the "Preferences" button. You will see the [user].ini file name in the lower left hand corner. You can also find your own [user].ini file from the Tools->My Preferences menu.

Solution 2:
If the error is received on the startup of QuoteWerks, note the database operation occuring on the QuoteWerks logo screen. More than likely it states, "Loading layout field definitions..."
Upon loading QuoteWerks, the system scans the databases of QuoteWerks and places them into an array in memory for use in the Layout Editor. The array it is building has a size limit. If the end user has tampered with a database of QuoteWerks -- more than likely adding non-standard fields to a database -- then this array will break as the number of fields will be outside the array's limit.
This array size was smaller in 4.0, but as of Version 5.0 the limit is 350. If the end user has non-standard fields in the database, this will not be supported by QuoteWerks Technical Support. The end user needs to either delete those fields, or if on an older version, upgrade to the latest version and build, and hope that it still does not exceed the limit of fields that QuoteWerks understands.

New Search