ACC: LimitToList Enforced Even When Set to No (122242)
The information in this article applies to:
- Microsoft Access 2.0
- Microsoft Access for Windows 95 7.0
- Microsoft Access 97
This article was previously published under Q122242
Moderate: Requires basic macro, coding, and interoperability skills.
SYMPTOMS
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.
CAUSE
Even 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.
RESOLUTION
In order to allow unique entries in a column box, make the first nonhidden
column in the combo box the bound column.
STATUS
This behavior is by design.
REFERENCES
For more information about the LimitToList property, search the Help
Index for "LimitToList property," or ask the Microsoft Access 97 Office
Assistant.
Modification Type: | Minor | Last Reviewed: | 1/26/2005 |
---|
Keywords: | kberrmsg kbprb KB122242 |
---|
|