>>Has anyone managed to work around this? I have found not a workaround, but a much better solution for my particular case, but in general, I think I may use this Scatter Name somewhere, IF it behaved.
>
>
>The behaviour you describe is exactly what I would expect it to be. I think they left scatter in only for backward compatibility. If I understand correctly, in VFP you would place your tables or views in the Data Environment and let Buffering handle all the functionality (and more) that we used to get with Scatter and Gather.

I said I've found a better solution than this (actually added a property to keep the old value for all of my control classes, and planning to make it two values), and sure won't try to reproduce the scatter/insert-from-memvar method of populating the tables with values from forms which I use in FPD, when we have buffering and other bells and whistles now.

I just wandered why the hell MSFT bothered to introduce a scatter-into-object feature, if scatter was altogether obsolete (or will be soon). The misbehavior I've noticed happens if I want the Scattered object to be a member of a form. Maybe I didn't try all the ways.

>If you need to know the old values of all the open tables in a form, you would be interested in checking the methods, OLDVAL() and CURVAL(). Depending on the situation (single vs. multi-user, tables vs. views), these will probably do just what you describe.

I prefer one which won't be depending on the situation, but then it's my job to make it, and these functions are good candidates to be used while making.