Technote Number: 1247123
Problem:
These errors occur in cases where there are 32,767 (32K) or more elements
returned by the @Db lookup. The issue occurs regardless if the returned lookup
is reduced in size (for example by using @Subset or @Unique). This issue has
been reported to Quality Engineering as SPR# JSHN6QPU38.
Workaround
The only workaround is to reduce the number of documents returned by the @Db
lookup. When using an @DbColumn, you can use a selection formula to reduce the
number of documents in the referenced view. When using an @DbLookup, you can
either use a more specific key value in the lookup, or a selection formula to
reduce the number of documents in the referenced view.
Supporting Information:
In Notes 6.0 and later, lookups can return greater than 64K as long as the
resulting data set is then limited using formulas or functions, so that less
than 64K of data is returned to a field or the Notes user interface.
There is unexpected behavior in cases where the @IsError function is applied to
lookups which return more than 64K worth of data. For more information on this
topic, refer to the document titled "@IsError check does not work as expected
with @Db lookup functions that return more than 64K"(#1233623).
A regression issue also occurs, specifically in Notes/Domino 7.0.1, where
lookups that return more than 64K always return an error even though the result
set is limited to less than 64K via a formula or function. For more
information on this issue, refer to the following document: "@Db lookups that
return greater than 64K always return an error even when result set is limited
to less than 64K" (# 1231611). More >
|  |
|
|
|
|
|