Hi Gerry

I guess now I am aware of this "feature" I will start ensuring that I only ever assign Integer values. Thanks for your clarification of what was going on.

Simon

>>I understand what you are telling me but it does strick me as a little strange that it works differently on a form. The default scalemode is pixels so I would expect the control to use pixels even when it is not contained on a form.
>
>The control is using Pixels; you are simply supplying the initial value in Foxels (when using a non-integer).
>
>And the translation from Foxels to Pixels is also not really random; it is based on a number of factors including FontName, FontSize and FontBold. And in the absence of a Form, _SCREEN comes into play, in terms of how "row heights" and "column widths" are determined when translating Foxels to Pixels.
>
>>I guess I will just have to ensure that I only assign integer values so I avoid this conversion process.
>
>A Foxel is "about" the width of a character; it can work for you when specifying textbox widths, etc. You just have to be aware of when it is appropriate to use.
>
>>So if what you are saying is indeed try then this is NOT A BUG but simply the way VFP works.
>
>No, it could very well be a bug; it's been around since VFP 3.0 (I think).
>
>I just consider all these "features" the price of working with VFP; not many days go by when I don't uncover "something". A major part of my coding in VFP is "defensive".