adding items to form list box not showing item text

[mayhem]

Hello,


I'm new to access, so please be patient.

I have a form with a dropdown box. I have a listbox on the same form that starts disabled.

On change of my drop down box, I want to populate my (multiselect) listbox with items, relative to my drop down box field.

In design mode I have my drop down box created and my empty listbox (with multi select set in properties).

My drop down box is populated by a query and works right.

I have edited the vba for the on change event of the drop down box to enable my listbox, I then grab the list box item count and use a fit loop to RemoveItem all items.

Then I run a query to get new values based on the value in my drop down box.

I then use the list box additem method to add items to my list box based on the record set. As a debug, I use msgbox to print my record set value and it appears correctly.

When running my form, and changing my drop down box, I can see that my listbox is adding items because I can use the multiselect functionality, the only problem is that I don't see the item labels. Wtf. I am using default settings, I tried setting font to black from some shade of blue, etc.

Anyone know why the labels aren't showing?

I'll post my code tomorrow, in not at work right now. Posting from my phone.

[Micron]

Your terminology is a bit confusing, but aside from that it sounds like you should start over as you're making this way too difficult. You say your "drop down box" (combo box) item list is a query (thus the combo box has a row source and not a value list) and it's working? Your listbox rowsource should be a query that uses the combo box value as criteria, and in the After_Update (not on change) of the combo, you requery the listbox. Maybe add a message box if the action produces no records. As for labels - don't know what you mean as a listbox doesn't have labels. Maybe you mean row headings? Or do you mean there is another column that you're not seeing that you're using to describe ("label") the row value.

[mayhem]

Yes I have a combo box for my first control. By label, I guess I meant row heading. I'm assuming when you use the additem method of listbox, the string you give it as an argument is the one that's suppose to appear in the listbox. That is the label I was referring to.
I'll try changing to the after_update event, although I don't see why on change wouldn't work. For example, I get the value of my combo box and use a message box to display it on change and it gets the value fine.

[Micron]

A row heading is not a list item, so you cannot add it. The 'Column Heads' property of a list box or combo box is what controls the appearance (or not) of headers. You can use alias names for fields in the underlying data source if the field names are not appropriate for labels. As for the event you chose, the on change event occurs whenever the value of the control changes. This means if the user can type in the control, it fires after each key press. That's why the After_Update event is the better choice for handling control value changes in your case, especially if doing the other means you're going to end up trying to populate a listbox based on partial values.

[mayhem]

A row heading is not a list item, so you cannot add it. The 'Column Heads' property of a list box or combo box is what controls the appearance (or not) of headers. You can use alias names for fields in the underlying data source if the field names are not appropriate for labels. As for the event you chose, the on change event occurs whenever the value of the control changes. This means if the user can type in the control, it fires after each key press. That's why the After_Update event is the better choice for handling control value changes in your case, especially if doing the other means you're going to end up trying to populate a listbox based on partial values.

oh i see, I did not realise that about the onChange event, i've only used onChange in excel and it works differently.

[Micron]

I too have been frustrated by the differences in Excel and Access vba, such as when I discovered that an Excel form is not called a form (at least not in Excel vba).
You would have thought they could have been on the same page with that one.