>>Naomi,
>>
>>>I was just thinking that I would have to use character, e.g. unbind in gotfocus, let the user type, then replace in lostfocus...
>>
>>FWIW, Megafox book has an extensive numeric-textbox class for calculator-type input, and it relies generally
>>on this approach. I use the Visual FoxExpress framework, and could not make it work acceptably
>>within that context. I ended up implementing an unbound character-type numeric textbox that, in turn,
>>updates a bound numeric textbox with Visible=.F. On the minus side, I did not like having to settle for
>>using 2 controls for a single task. On the plus side, I was able to fine-tune very well the character-type
>>numeric textbox to trap invalid user input and issue detailed error messages.
>>
>>-mark
>
>Mark,
>
>Perhaps your way is better that what I tried to implement, because even if I change information the Save button doesn't become active, which probably means the changes are not detected.
>
>Also I noticed that the form shows 'Information Saved' message before I do anything at all. Don't remember if I was getting this error before.
>
>I'll try to get the older version of this form and see if this is indeed the result of my changes.

I was having similar problems with unbinding, changing to character, changing back to numeric and then rebinding.
I spent a fair amount of time trying to trace the problem. My conclusion was that the problem was not with VFE, but
with the buffering somehow getting screwed up, although I could never figure out exactly how. Bottom line was that
changes were not always properly detected, and cancels did not revert values properly under some circumstances.
I finally declared defeat (which I hate to do) and went to Plan B. As I noted above, it's less elegant, but it works the way
I want it to.

-mark