>Dragan,
>
>Yes, I've used it in a classlib documentation tool, that builds a multilinked data structure and I use a member property that gets some of the classlib/form fields scattered to it. This way I can pass the class around as an entity. Try this:
>
>use grid1 && test table with colums c1, c2, c3, c4
>
>o1 = createobject( "data" )
>scatter name o1.oDataRec
>
>o2 = createobject( "data" )
>skip
>scatter name o2.oDataRec
>
>? o1.oDataRec.c1
>? o2.oDataRec.c1
>
>define class data as custom
>   oDataRec = .null.
>enddefine
>

Tried (having adjusted field names for a table of mine) and - is this the only way to get it to work? I mean, defining a null property in a class and scattering into it. I've tried .addobject() to a form, and some things more, but none of them was acceptable as a name to scatter to.

I'll play around it some more, may be useful for something. I've had an idea of making an array of these to keep memory images of the child records in a grid, so any recalculation could be performed on the array instead... I probably won't do it that way at all, but the idea seemed worth thinking over at first. Sometime it may be a valuable ace in my sleeve - having a spare technique never hurts.

Thanks anyway - I'd never have found this alone. VFP is to large for any single programmer to find all of its back corners.