Dragan,

I don't think you can scatter to a property that has beeb assigned a type like C or L or N. So it just takes giving the custom property a value of .NULL. on the property sheet.

At first SCATTER NAME seemed like a really cool thing from a FP2.x viewpoint, but the data buffering it's not really needed in day to day forms. It can be handy though in creating a packaged object to pass table rows around as object entities.

>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.