Tore,

For unbound textboxes, this is actually the best way to have the textbox.Value set to the correct type. It's equivalent to setting it to 0 or {} to set it N and D respectively.

But no, it's not worth much more effort. It's not a bug, it's just an error in the way Fabio has hosed up the initial value.

>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.