J
Jon Furman
Hello everyone...I've run into a problem that I'm suspecting is an Access
bug and am wondering if anyone else has run into it. Here's the deal I have
form with two listbox controls, what I want to do is have the second listbox
update it's contents based on the selection of the first listbox. So far so
good...now I also want the second listbox to always have at least one item
selected. I'm using VBA code to make all of this happen, so on the
afterupdate event of the first listbox I take the selected value and
programmatically reset the data source for the second listbox..that works
fine. Now I use the following code to make the first item selected in the
second listbox:
Let Me.lstBox2.Selected(lRow:=1) = True
That line of code completely destroys the workings of the form. The second
box becomes unresponsive and won't update and some areas of the form start
responding to click events that have no procedures assigned (I get an
hourglass). I've tried several permutations but none of them fix the root
problem although some of the things that I've done have changed the symptom.
Very very strange. All that's required to reproduce the issue is a form with
2 listboxes and the one line of code above. Anyone else seen this? If anyone
want's to actually see the problem in action I can post a sample MDB on a
webserver and you all can see the details. All ideas are appreciated. Thanks
all.
Jon
bug and am wondering if anyone else has run into it. Here's the deal I have
form with two listbox controls, what I want to do is have the second listbox
update it's contents based on the selection of the first listbox. So far so
good...now I also want the second listbox to always have at least one item
selected. I'm using VBA code to make all of this happen, so on the
afterupdate event of the first listbox I take the selected value and
programmatically reset the data source for the second listbox..that works
fine. Now I use the following code to make the first item selected in the
second listbox:
Let Me.lstBox2.Selected(lRow:=1) = True
That line of code completely destroys the workings of the form. The second
box becomes unresponsive and won't update and some areas of the form start
responding to click events that have no procedures assigned (I get an
hourglass). I've tried several permutations but none of them fix the root
problem although some of the things that I've done have changed the symptom.
Very very strange. All that's required to reproduce the issue is a form with
2 listboxes and the one line of code above. Anyone else seen this? If anyone
want's to actually see the problem in action I can post a sample MDB on a
webserver and you all can see the details. All ideas are appreciated. Thanks
all.
Jon