My idea was a "push" to each instance of the form -- your idea of the timestamp is a "pull". The idea of the push was to mimic the clipboard -- all share the same data; since each "clipboard" cursor resided in a separate datasession, I was looking to push the copied nodes. I think your idea is better with the timestamp and let each form get it on demand (pull) -- less overhead required and I don't have to worry about collection management of the form references. Thanks.


>I think you only need 2 properties for the objecy: XML and timestamp. You'll also need timestamp property on the form. In the activate of the form check timestamp property of the form against the object and update forms cursor only if XML changed.

>>>Would CURSORTOXML() and XMLTOCURSOR() work for you? Check also How to pass cursor between two VFP datasessions (without using XML) FAQ #29297
>>
>>I thought about using an object (new property at the _screen level) and moving via this by a scatter/gather as in FAQ 29297.
>>
>>Rather, I think I like your idea of using CURSORTOXML and XMLTOCURSOR. My thought is to define a custom class which has a collection property for each form to register with at Init and unregister at Destroy. This gives a handle back to each form's datasession. Another property would be defined with an assign method -- this assign method would handle updating each form's datasession. Each form would then assign the XML to the property which then moves it to the other forms.
>>
>>See any holes, problems?