This article applies to:
This item was fixed in E-Prime 1.1.
Using List.SetNested does not behave as expected. The result is that it affects the level one more than requested.
For example, calling List.SetNested 15, "MyNestedList" will actually set level 16 to "MyNestedList"
Upgrade to E-Prime 1.1.
This workaround is intended only for those who are unable to update to the version of E-Prime that contains the bug fix:
Use zero based indexes in E-Prime 1.0.