View Single Post
 
Old 08-18-2014, 04:23 PM
CoolBlue's Avatar
CoolBlue CoolBlue is offline Windows 7 64bit Office 2013
Advanced Beginner
 
Join Date: Jun 2014
Location: Australia
Posts: 40
CoolBlue is on a distinguished road
Default

Quote:
Originally Posted by whatsup View Post
Hi CoolBlue

I haven't checked if the file is corrupt neither where the bug sits. Myself I'm hardly using the rowsource-property and never the value-property (on ListBoxes !!!). Therefore my advice generally is - unless you intend using the listbox for reading purposes only -, don't go with the rowsource but use the list-property.
Using ListIndex in reading from the Listbox and marking a "value" makes both much easier as bothering with value.

Hi Whatsup

Based on the research I did, I think your original post was the best solution. My feeling is that the root cause is just a bug in VBA.

I haven't seen problems with .RowSource although, you do need to be careful to fully qualify the Address of the range; I use .Address(External:=True) to take care of that. Have you noticed specific problems with it when using ListBox, or do you just generally avoid it because of the buggy .Value behaviour?
Reply With Quote