Hi Gerry

I have just discovered this only happens when the control is not on a form. However, I still do not understand why it should happen at all. I am assigning the value and it should accept the value regardless.

Perhaps you are wondering why the control is not on a form. That is because it is part of a container that will render itself in DHTML for display in the browser. I was planning to avoid the extra overhead of using the form since it was not needed.

Simon


>Assigning non-integer values to control coordinates and dimensions usually causes VFP to assume it is working with Foxels even though the .ScaleMode is set to Pixels.
>
>>If you assign a non-integer value to the Width or Left etc. property of a control the property is randomly assigned another value. If you use an integer value everything works fine.
>>
>>For example:
>>
>>lo=CreateObject("textBox")
>>lo.Width=160 && Work Fine
>>
>>lo.Width=25.0 && sets the width property to 175
>>
>>This does not happen in VFP 7.0. I found this problem when converting an app from VFP 7.0 to VFP8. I was dynamically sizing command boxes and noticed the sizes did not work in VFP 8.0 and finally traced to non-integer values being assigned to the width property.
>>
>>This looks like some kind of C++ type conversion problem.
>>
>>Simon