David,

no matter what happens here, I personally think it's a waste of time to really dig too deeply into this, don't you agree? I can think of no situation where setting a currency directly into the value property of a textbox in the property sheet makes any sense. In fact I can not recalling ever having set a value at all for a textbox, because I always binds it to a property or a field, or I set in in code.

>Tore,
>
>If you look in the properties memo you'll see " around the value.
>
>If you reset to default and then type in $0 as the value and close the designer you'll see the properties memo has it as a currency constant which will always display Y correctly as my form indicates.
>
>I think it must have to do with some sequence/validity of his SET POINT at various points of time that has caused VFP to say, wait this must be a string because it doesn't fit the current currency constant format.
>
>>I tested Fabio's small description, and in deed the vartype(this.value) showed C. I also tried to change the value from the command window, and the same happened. The value showed and acted like currency, but VFP reported character. Setting NTOM(0) in the property sheet made vartype report Y. And I definitively can't see that Fabio has done anything illegal, although I never would set the value of a textbox to $0 in the property sheet myself.