tag:blogger.com,1999:blog-8166852.post5155626569901003494..comments2009-07-29T19:36:21.917-06:00Yakko Warnerhttps://profiles.google.com/102705077104052556673noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-8166852.post-7025906501155355402009-07-29T19:36:21.917-06:002009-07-29T19:36:21.917-06:00I deleted it intentionally. I wanted to make sure I was looking at database IDs and not, say, index or sequence numbers. If there was no 5 in the database but I saw a 5 in code, then I would know the numbers had <i>nothing</i> to do with the actual IDs.<br /><br />I played with it some more and noticed that, somehow, the ComboBoxes&#39; Sorted property were set to True (instead of the default False — don&#39;t know how that got switched, I know I didn&#39;t change it).<br /><br />I did switch that to False, but it was long after I removed the code checking SelectedValue, so I don&#39;t know if that would&#39;ve fixed it. If that is what caused it, then it would appear Sorted sorts the Values so they no longer are in sync with the actual items.<br /><br />Oh yeah. <i><b>That&#39;s</b></i> useful.Yakko Warnerhttp://www.blogger.com/profile/12276550157896918123noreply@blogger.comtag:blogger.com,1999:blog-8166852.post-84051892697183172192009-07-29T17:27:44.788-06:002009-07-29T17:27:44.788-06:00I see 1, 2, 3, 4, 6, and 7 - whatever happened to 5?Spencerhttp://www.blogger.com/profile/13295028114725152342noreply@blogger.com