form failure after adaptation - pageframe problem "cyclical"

form failure after adaptation - pageframe problem "cyclical"
Paul
All

Aug 12, 2019 @ 10:26pm

Hi,

A complicated form class was adapted and seems to be fine when opened in design-time, but it fails to open at runtime :

The problem seems to be related to the form having nested pageframes, most of which used to have a class of "pageframe" and some had a class of "subclass_of_pageframe"; the former "pageframe" ones now have a class of "xxxpgf" after adaptation.

There are some other forms with a similar structure and they are fine!
These pageframes are on the form at design-time, they are not added programmatically.

I have edited the .vcx as a table and changed the former "pageframe" ones (now "xxxpgf") to "subclass_of_pageframe", as they should have been in the first place, but this hasn't fixed the runtime problem.

It seems like some sort of corruption of the .vcx, but I have not found the error.
Has anyone seen this problem and know how to fix it?

.
..
EDIT : For anyone else who encounters this problem, this is how I fixed it :

copy all controls on the pages under any troublesome pageframe to a temporary form
delete the pageframe
add a new pageframe to the form, using the correct class
recreate the pages
copy and paste the controls from the temporary form to the newly created pageframe in the first form
ensure any code in the recreated pages is reinstated

Once I fixed the design-time pageframes with that problem I found that another pageframe, which is added during runtime and could not even be opened at design-time without error, also had the problem.
I fixed that by editing the .vcx as a table and amending the content of table.Properties.
On one pageframe (out of 10), table.Properties was wrong; although table.Class had been adapted to "XXXpgf", table.Properties contained code like "Page1.name = "blah" - it should have contained "XXXpag1.name = "blah".

Thanks
Paul