Is accessing behaving correctly?

[dpdeleon]

I"ve created a value list programmatically for a drop down by concatenating
values. I've noticed that when I use a list such as

rowsource = "item1, item2, item3"; item4;item5

item1, item2, and item3 are separated in the dropdown

Whereas

rowsource="item1/item2/item3";"item4";"item5"

keeps item1, item2, and item3 together in the dropdown.

Is this correct behaviour on the part of Access?

 

[Dirk Goldgar]

I"ve created a value list programmatically for a drop down by
concatenating values. I've noticed that when I use a list such as

rowsource = "item1, item2, item3"; item4;item5

item1, item2, and item3 are separated in the dropdown

Whereas

rowsource="item1/item2/item3";"item4";"item5"

keeps item1, item2, and item3 together in the dropdown.

Is this correct behaviour on the part of Access?
Neither

rowsource = "item1, item2, item3"; item4;item5
nor

rowsource="item1/item2/item3";"item4";"item5"

is valid VBA code, so what does your actual code assigning the rowsource
look like? This works for me:

Me.Combo0.RowSource = """one,two,three"";four;five"

 

[CQURDEN]

is valid VBA code, so what does your actual code assigning the rowsource
look like? This works for me:

Me.Combo0.RowSource = """one,two,three"";four;five"

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)