I have a dropdown box with code in the SelectedIndexChanged event. However, the event does not fire on every change because the index value takes the value of the listitem. Why is this? Can someone please shed some light on why this is happening. To offer more insight, I have about 20 items, half of them have a value of 1, the other half have a value of 0. I add them to dropdown by setting a dataset table as the dropdown data source.

Consider this...
<select name="mySelect">
    <option value="1">One</option>
    <option value="1">Two</option>
    <option value="2">Three</option>
    <option value="2">Four</option>
</select>
You select "One" and post. Request.Form("mySelect") = 1
You select "Two" and post. Request.Form("mySelect") = 1
If mySelect.LastValue <> mySelect.CurrentValue Then
    Fire off SelectedIndexChanged event.
End If
How does it know the difference?

The selected index value does not come from listitem.value, it's figured out based on what the listitem values are in the sequence stored in viewstate. If there are duplicate list values you'll only see a a change when you switch to an item that actually has a different value and at that the selected item will be the first item to have that value. All listitems must have a unique value.

Peter

Thanx Pete. You confirmed exactly what i thought, which by the way is terrible. I also appreciate your code sample, however, i think when i bind the dataset to the dropdrown, i will use an incremental value to append to the value of the list item, and take off the appendage when i need to.

Thanx again for the quick response.

Is there a reason that you don't have unique values? That's kind of the point of the value attribute. The text part of the select option is just for the human's. If the text part of your listitem is also the value that you are eventually going to use, you could just set the value attribute of the listitem to the same field in your databind settings.