tcl.wselect
Same as 'select', but uses indices if present.
Description
a Pick/BASIC simulation of the 'select' verb that additionally exploits b-tree indices.
For instance:
sselect entity by name
In this example, only one attribute is specified. If there happens to be an index defined on the attribute referenced by 'name', the response is practically immediate, since it can fetch the pre-sorted b-tree for the requested list. If the sentence were to contain a more complex expression, such as in the case:
sselect entity by zip by name
Again, assuming that indices are defined on both the 'zip' and 'name' field, Access processes the sentence as though the indices were not even there.
In addition, Access does NOT use the indices if any wildcards ('^') or string-searching characters ('[' or ']') are present in the sentence.
In some rare and peculiar cases, 'wselect' may be faster than the 'select' verb.
See Also
User Comments
What do you think?
Share your experience or ask a question by using the form below.
Login to leave your comments.
