It is a quite neat trick if it is legal. (that self of a nested record points to the nested record, not the encompassing one)
I would hope it would be legal, I've doing such tricks for some time now and the SELF. It would be broken if not pointing to the immediate record when referenced which btw is also part of the parent record that over hangs at the end. That is the intent here.
This is to support Structs (Records) with empty count arrays at the end of the struct(record).
The test app I posted here is just a model of a much larger app with a lot more content in the records of course and I did last night move it to the PC with the Trunk install and that seems to work but the app as a whole appears to be getting bad data when using 3.2.x and I need to determine where this is taking place so I can move on.
BTW, I discovered that the OBJECT model still supports this and can be used that way too instead of an advanced record, meaning the tail record can be an object instead.
The old original code was this way to support the over hang at the end.
Thank you much for testing, all of you.