>Hi all,
>
>I have the strangest problem. I was making a lot of changes on a form with pageframe and test it, it resulted in dreaded fatal error C0...5. I checked the log and there was no information. I started over again by deleting all FoxUser.*, recompiled .dbc, cleaned up, etc... and restored the old form. I made a change, saved it in backup, tested it, one at a time, to pinpoint the cause of the fatal error. All changes ran fine but then when I added a new page (PageCount was 6, changed it to 7), bam, fatal error! Just ONE simple change! A new page! I also tried This.Refresh() in the click method to no avail. Page 7 has nothing in it. For the life of me, I do not understand why adding a new page caused the fatal error.

I also have one such class with lots of controls on each page, and when one more was needed, we had to add it at runtime - adding it in the class would break it each time (VFP9 though... not much of a consolation).

The solution was to save each page as a class, and add it at runtime, from pageframe's init. Which also makes it easier to select which pages to instantiate if not all were needed, in which order (the .pageorder had a non-default value for many of the pages, very confusing in design mode). In the end, it sets the .activepage=1 (though a different value was possible - e.g. a saved one).