>>>>>>>Now, since there is exact same code in all pages, it will be nice to bind them to form's custom method. However, how do I prevent users to leave the page using this technique?
>>>>>>>
>>>>>>
>>>>>>Why not use a Page class instead of the default page?
>>>>>>
>>>>>>Tamar
>>>>>
>>>>>This is a novel idea. I guess I haven't thought about it as I never used page class before. Do I need to create page class in code? Also, the form is already designed, how can I change page class?
>>>>
>>>>Hack the vcx and set the memberclass of the pageframe to your new class.
>>>>
>>>>Note that inits of the member pages will run _before_ any other code, except property evaluations. Also, properties of the pages, during this .init() will be the default properties, not the ones set in the pageframe, so any code relying on order of init firing may be thrown off. Do some tracing to see how this works.
>>>
>>>How exactly you subclass a page class?
>>
>>as every vcx class.
>>
>>convert a native page member to a memberclass page
>>is not trivial.
>>backup the vcx before to start
>
>Ok, I created the page class (didn't know we can subclass page easily). In the form I'm using PageFrame class. If in this page frame class I set MemberClass properties, will it automatically "fix" my existing form?

NO.