I have a combo box that I'd like to use MultiSelect. Can I do that or does it need to be a list box? The list box doesn't have the look I prefer.
I have a combo box that I'd like to use MultiSelect. Can I do that or does it need to be a list box? The list box doesn't have the look I prefer.
Combobox would have to be bound to a multi-value field. I do NOT advise using multi-value fields.
How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.
combos are for 1 value.
Like @June7, I would also strongly recommend against using multivalued fields
However, if you really want to know how to do this, see Multivalued Fields - Mendip Data Systems. Hopefully the article will be enough to dissuade you!
Multiselect listboxes work in a different way and do not cause any problems
Combo boxes do not have a MultiSelect property. List boxes have the MultiSelect property.
Note that there is a difference between MultiSelect and MFV (multi-value-fields). Multi-value-fields are considered a BAD Design option.
What do you want to do with the MultiSelect list box??
EDIT:
Oops, just saw your post #5.
OK, if you make multiple selection in the list box, the list box is still bound to only one control control source (one field in the record source.
If you want to make multiple selections and save those selections, you will have to write code to loop through the selected items and write the values to a field in a table.
I would call that a built in Sort/Filter dialog.
A list box control has a MultiSelect property - you can see it in the control property sheet -> other tab.
A combo box control does not have a MultiSelect property - you can not see that property in the control property sheet -> other tab.
OK I could have used a better pic. Still its the same type of control, just added to a context menu.
Not all properties are exposed in the sheet. Google multi select combo box - you'll get plenty of results because they do exist. They were introduced in 2007 to deal with Sharepoint lists. They can only be used with MV fields AFAIK.
Is this better?
Link with pics of mv combo
https://support.microsoft.com/en-us/...rs=en-us&ad=us
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.
OK, but I have never used Sharepoint and probably will never use it.
And using MFV's violates the "Rules of Normalization" - I never have used MFV's and never will. Colin has an article "Multivalued Fields . . . and why you really shouldn't use them!"
Sooo, using standard Access, not Sharepoint and not MFV;s, I still assert that a combo box control on an Access form does not have a MultiSelect property. (I wish there was a tap dancing smiley)
You're preaching to the choir.
OK, you win.
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.
I googled (actually I use DuckDuckGo) "Multiselect" property and Micro$oft says the multiselect property only applies to the "ListBox Object".
I still hold that a look up field at the table level, combined with a MVF, is NOT the same as a combo box with the multiselect property.
Both the look up field and the MVF violates the rules of normalization.
However, I will give you that it does look like a combo box control with multiselect capability....
We both win.....agreed??
@ssanfu, could you please drop Bill a line and see if he'll remove the documentation references to a multiselect combo box and get him to replace it with what you think is correct? You can refer to the following portions of his on-line references - thanks in advance!
ComboBox.ItemsSelected property (Access)
This hidden collection can be used to access data in the selected rows of a multiselect combo box control.
Syntax expression.ItemsSelected
BTW, I don't see what the multi select property has to do with this. A control is not a property. I'll give you that a combo doesn't have that property (taking your word for it) but it I'm sticking with the notion that they DO exist, albeit they have the ItemsSelected property instead of multiselect property. This would be because a listbox can be either regardless of what it's bound to. These combos have the ItemsSelected property instead, and that only applies when it's bound to a mv field.ComboBox.ItemsSelected property (Access)
You can use the ItemsSelected property to return a read-only reference to the hidden ItemsSelected collection. This hidden collection can be used to access data in the selected rows of a multiselect combo box control.
Over and out.
Last edited by Micron; 05-27-2021 at 07:53 PM. Reason: added comments
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.