This would be a problem for me if pagenames were not modifiable. Hopefully it only has to do with subclassing perhaps? I have not experienced this error yet. I create forms that have more than 20 pages but the actual pages displayed to the user are determined on the fly - typically only 5 or so. In the init of the form I call a form method that changes the pagenames that are displayed to the user to match the current order of the pages so code in my keypress event will always run correctly. I do this so I can set focus to the correct page and control on the page when the user presses the pageup or pagedown keys, etc.

Is this only ocurring during development? I have run this form in VFP9 beta without any problems so far but I will do more testing to see if it occurs during runtime.

>Hi All
>I discovered a Bug/bad Behaviour subclassing forms.
>Following the below istruction is possible to corrupt class:
>
>1) Create a class library with a form containig a pageframe
>2) create a second class that derives the first class and add a control on a page of pageframe, so save the class
>3) Modifying the second class and change the name of the page where yoiu place the control, so save teh class.
>4) try to modify again the second class .... you'll see an error.
>
>Infact the last save don't save correctly the modification of the name of the page, but the control have the right Parent link.
>
>My opion is that the name of the pages should be not modificable.
>
>Any other opinion ?
>Thanx in Advance