>This technique is legacy fox 2.x support. Binding controls to variables works, but has unpredictable results. Especially when variables are modified thoughout various methods. A better way to accomplish the same is leave the control unbound, and access its value property through code. If he leaves it this way, be sure to use PRIVATE declarations throughout your methods to avoid contention problems.
>
I thought perhaps that might be the case. Something that is available now but who knows how much longer VFP will continue this legacy support. I think he would be better off using properties of the form to store values.

Dan