>>>VFP3 had a problem with ampersands in comboboxes showing up in the display as an underline indicator rather than as an ampersand. In other words, if the value was A&A, it would be displayed in the text display as AA with an undercore under the 2nd A.
>>>
>>>I have to do some work using 3.0b, and I can't find a workaround for this. I've checked Deja News, but while the question is asked a few times, it is never answered. On Microsoft's site, the problem is acknowledged as a bug in 2.5 and 2.6, but there is no mention of it in 3.0.
>>>
>>>Has anybody every found a way to deal with this? Microsoft's 2.6 suggestion of typing a double ampersand into the data is unacceptable.
>>>
>>>Suggestions?
>>>
>>>Thanks
>>>
>>>Alan
>>
>>.caption = "A" + chr(38) + "A" worked for me.
>
>sorry, got to fast with response. This worked for a command button caption.

Whew! Thank goodness. I thought I must have a faulty combobox with no 'caption' property. ;)

Anyway, it's the thought that counts.

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