Solved Perils Referring To A Value In Listbox By Referring To Listbox Itself (Not .SelectedItems)?

[dalski]

Everywhere I have read says to use the .ItemsSelected property of a listbox to obtain the value. Looping through on multi-selections.

On a single selection listbox it seems that referencing the listbox itself will return the bound column value. Also if there is nothing selected it will return a null, & return a null if the listbox is empty. I would prefer to use this lean syntax if there are no negative effects I am ignorant of - so I ask a friendly expert; is it a bad idea to reference the listbox directly for it's value?

 

[cheekybuddha]

is it a bad idea to reference the listbox directly for it's value

No. It is good.

This is how you should refer to the value of a single-select listbox

 

[dalski]

Thanks @cheekybuddha

 

[moke123]

Also if there is nothing selected it will return a null, & return a null if the listbox is empty.

Just be aware of a little quirk with a single value listbox. If you set the value with code it can return that value even though it is not in the listbox.

 

[dalski]

Thank you @moke123

 

[Pat Hartman]

so I ask a friendly expert; is it a bad idea to reference the listbox directly for it's value?

That is not a valid question. You need to distinguish between multi-select, which creates an array and so you use .itemselected and single select, which does not create an array and so you can reference the ControlSource directly either as Me.MyList or Me.MyList.Value

In Access VBA, the .Value property is the default and so is generally omitted. In VB, the .Text property is the default for controls.

 

[MajP]

Everywhere I have read says to use the .ItemsSelected property of a listbox to obtain the value.

I cannot imagine that someone suggested using itemsselected for something other than a multiselect listbox. I have to imagine any search on the internet would say to reference the listbox value property for a standard single select listbox.

Although you can go through itemsselected on a single select, it would be cumbersome and a round about way.

The syntax on a single select would look like this using itemsselected
Me.List0.ItemData(Me.List0.ItemsSelected(0))
vs
normal method of
me.list0