>The VFP architects could have simply added a property on Custom objects that determine "shall the results of new queries created with this object be created in the current DataSession, or the original Data Session which was active when the object was created." That would be most useful to me at this time.

IMO, it's good that they didn't. It's not just the custom objects, you can have cursor making anywhere, and so it would be yet another property to set. Not to mention that it would also raise the question "how many levels deep?" or "if some of the callers on the stack don't have this property set, should it still work"?), what about other DS related issues? What if an object with that property set changes the date format, which DS should be affected? Etc etc...

It's enough that an object living in a different DS inherits the private variables from the stack (so we have a mix of environments - variables visible all the way down the stack, cursors and settings separated by DSs), throwing in a setting like that would make our lives a madhouse.