In my example, the value is a KeyID that the user never sees. All they see is the display value of the combo. If the value and displayvalue are the same, then there is no confusion. My display values are usually descriptions while the values are integer keys.

>I changed that, but it's kind of questionable. One thing is what the user would like to hear - Value or DisplayValue ? (I could customize that)
>And another question is that when I click on combo, Agent starts speaking and I quickly change the value from "Fruits" to "Vegetables" as the agent speaks, so by the time it proudly pronounces "Fruits" the combo already shows "Vegetables".
>
>
>>Way cool, Nick!!! My suggestion would be to modify the speaker to give the DisplayValue of combos instead of the Value.
>>
>>>Hi All,
>>>
>>>I just uploaded the new file for the Files Section. This app is called FoxSpeaker.
>>>
>>>FoxSpeaker is an applicaton that allows you to add speech capabilities to your VFP forms on a control-by-control basis. Any form can be turned into an interactive demo or tutorial easily. FoxSpeaker does not require any changes to your forms except adding one button to switch FoxSpeaker on/off.
>>>
>>>FoxSpeaker is written in Visual FoxPro and uses Microsoft Agent 2.0 ActiveX control. It is compiled as VFP 5 EXE, so it works in both VFP 5 and 6. Please see FOXSPEAKER.DOC. Demo form is also provided.
>>>
>>>When you enable FoxSpeaker (assuming Microsoft Agent and speech engine are installed) the Microsoft Agent character will appear on your form, and as you click on the form controls it will move to the control, highlight the control with the red rectangle and tell you the value and comment which you may add with Right Click on your control. You may click/add comments to any form control, including disabled controls, labels, shapes, containers, grid columns, etc. When FoxSpeaker is enabled your form stays fully operational.
>>>
>>>I would appreciate any feedback/suggestions/bug reports.
>>>Thank you in advance.
>>>
>>>Nick