ACC: LimitToList Enforced Even When Set to NoLast reviewed: May 7, 1997Article ID: Q122242 |
The information in this article applies to:
SYMPTOMSModerate: Requires basic macro, coding, and interoperability skills. When you type a unique value in a combo box and then press ENTER, you may receive the following error message even though the combo box's LimitToList property is set to No:
In Microsoft Access 7.0 and 97: The text you entered isn't an item in the list In Microsoft Access 2.0: The text you enter must match an entry in the list CAUSEEven if the combo box's LimitToList property is set to No, Microsoft Access limits entries to those in the combo box if the first column displayed in the combo box is not the bound column. This behavior occurs because Microsoft Access stores the bound column value when you enter a nonbound column selection. If you could enter a new value for the nonbound column, Microsoft Access would have no value to store for the bound column.
RESOLUTIONIn order to allow unique entries in a column box, make the first nonhidden column in the combo box the bound column.
STATUSThis behavior is by design.
MORE INFORMATION
Steps to Reproduce BehaviorIn Microsoft Access 7.0 and 97:
REFERENCESFor more information about the LimitToList property, search the Help Index for "LimitToList property," or ask the Microsoft Access 97 Office Assistant. |
Keywords : FmsCmbo kberrmsg kbusage
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |