Fabio,

In this particular case it means that VFP evaluates the setting of the property when the form is first instantiated to define how the form will behave during the rest of it's lifetime. If ScrollBars is not > 0 when the form is instantiated the scrollable behavior is not enabled.

create form frmscrollable
change no properties
*run it
* then run this code from the command window
frmscrollable.addobject( "lbl", "label" )
frmscrollable.lbl.Top = 300
frmscrollable.lbl.left = 400
frmscrollable.lbl.Visible = .t.
frmscrollable.ScrollBars = 3

setting Scrollbars = 3 has no effect... since it was 0 when the form instantiated, changes to the property are ignored.

* close the form


modi form frmscrollable
set Scrollbars = 3
run the form

frmscrollable.addobject( "lbl", "label" )
frmscrollable.lbl.Top = 300
frmscrollable.lbl.left = 400
frmscrollable.lbl.Visible = .t.
*click on the titlebar of the form to cause it to activate, scrollbars appear

frmscrollable.ScrollBars = 0 && they don't turn off
* drag the corner of the form a little bit to resize it, the scrollbars now disappear

So if the scrollbars are > 0 when the form instantiates then, they can be manipulated at runtime, Which is documented by this line of the help file:

If you want to control scrollbar size at run time, specify a non-zero value for nType.

I am not suprised that scrollable forms have slightly different event sequences when compared to non-scrollable forms.

Personally I think scrollable forms are a horrible UI, I think it's much better to use a pageframe.

>
>The Scrollbars property setting is evaluated for a form when the form is instantiated.
>
>
>This put no new information, it is obvious:
>all property setting is evaluated when a class is instantiated
>
>On original post i write ( on help is little explain this )
>
>I open this thread for explain this:
>scrollable forms are not used frequently and have internal specific code,
>then they can have more hidden bugs respect to a normal form