>Hi Victor.
>
>>>So the 2 is still in the table that is the control source, right?
>
>But now...when the form is run...you don't see the 2! All you see is a blank. Now even though they can only select a 1 or a 3...the user still needs to be able to see the 2 because that is the current value of the table that is the control source...SURLY there is a way to do this...I'm tempted to make a textbox on top of the combobox to get around this...but that seems kinda like a lot of work and somewhat insane..heh...
>
>ANYHONE got a way around this? <<
>
>From Chapter 5: Combo's and Lists in "1001 Things You Wanted to Know About Visual FoxPro" (Akins, Kramek, Schummer) from Henzenwerke Publishing ISBN 0-9655093-3-8...
>
>So what if I want to bind my combo to a value that isn't in the list?(Example: CH05.VCX::cboSpecial and CH05.VCX::cboNotInList)
>
>The first question that leaps to mind here is "Then why are you using a combo box?" Combo and list boxes are used to limit data entry to a set of predefined selections. Permitting the user to enter an item that isn't in the list defeats the purpose of using a combo box in the first place. Having said that, we realize there may be occasions where this sort of functionality is required.
>
>HTH
>
>Marcia

ummmm...lemme get this straigt, you know a way around this problem and if I wanna know I gotta buy yer book? I've heard plenty of good things about the book, and someday when I'm not 1800 miles away from home at a client-site trying to resolve some problems I'll get it..but in the meantime I still would like to find away around the problem I'm having.