>The problem was that you were trying to use the Value property instead of the DisplayValue property. Value only applies when you have a controlsource.
Not true. It may only make sense (to some) with a controlsource, but it still applies.
In the form (or class) designer, this works quite well with listboxes. Why it doesn't in programmed classes doesn't make sense, IMHO.
I have plenty of listboxes with empty ControlSource, but have a BoundColumn (which is what goes into the Value) set to something other than 1. (e.g., movers) Checking the Value of these has never been a problem for me.
OTOH, using the DisplayValue could also solve Steve's problem.
Insanity: Doing the same thing over and over and expecting different results.
