In the early CQG API (versions 1.0, 1.1) accessing a non-existent collection item resulted in throwing an exception, the way it is usually done in Visual Basic collections.
Starting from version 3.0, CQG API can be adjusted to return "Nothing" in such cases.
The exception method remains, but now users can choose their preferred method.
When a non-existent item is accessed, depending on the CollectionsThrowException setting specified in CQGAPIConfig, the collection will do one of the following:
1. Return "Nothing" if CollectionsThrowException = False
2. Throw an "out-of-bounds" exception if CollectionsThrowException = True