>>Incidentally, I did try putting into the interactive change event, the following: This.DisplayValue = STRTRAN(This.Value, Chr(38), Chr(38)+Chr(38))
>>
>>Microsoft's 2.6 workaround was to have a double ampersand entered into the data. Unfortunately, I don't know if this works or not since the displayvalue and the value no longer match, so the displayvalue shows up blank. I can't tell the client to enter ampersands into the data as double ampersands. That has to be one of the worst suggested workarounds Microsoft ever came up with.
>>
>>Alan
>
>Yeah, anything that involves a problem with data like this one is a definite BUG that should be fixed. Do you have the same problem if the data is something like A & A?

Yes, the ampersand in data referenced by a combo box (in vfp3.0b) acts as an underline indicator for the next character. In the case above, the display shows up as "A _A".

Short of creating my own entire combobox class...

Alan