>If you are using a numeric controlsource you must set eh BoundTo proepty to .T. or else the value returned by teh combo will be the index for the selected item and not its value. VFP does the data conversion for related to controlsources. However, combos and list may only contain character data internally.

Sounds like VFP implements combos and lists with arrays (or cursors) it fills with elements from the designated rowsource, but these image arrays always represent their mirrored counterparts (in the rowsource) using character strings regardless of the data type of the rowsource fields. Furthermore, it seems like what you are saying is that even if the list.value is bound to a numeric control source, the actual type of list.value will be character regardless of the type of the control source?

All of this stuff regarding the actual type and value of the value property still has me a little confused. Let me ask a question in another way to see if I can get some clarity.

What general programming function does the value parameter serve w/respect to controls. Is it proper to think of it as the character buffer VFP uses as one is entering a value into a control? What are the general circumstances under which one accesses and/or modifies this.value as opposed to accessing or modifying the controlsource that mirrors it? Under what circumstances must one be careful about modifying this.value vis-a-vis the intrinsic use of same by VFP?

I want to take control of this.value, Jim, but I'm not real clear about what it actually is!