I haven't done anything with the new session object yet but have a situation where I think it would be useful. Here is the situation.

I have a form with a pageframe in VFP 6.0. The pageframe is designed to add a page and container object from an outlook style bar. The application has been running for over a year and everything works great. We are now adding more complex container objects which open and close required lookup cursors. The problem is we use the same cursors in many of these container objects and we currently use a different alias for each of the container object's cursors. Of course this is difficult and messy to track. I would like to have each container object create it's own session to simplify data handling.

My question is about the scope of the session object in regards to the container object and bound controls within the container object. Will the container inherit the DataSessionID from the newly created session object? Will the controls bind to the data in the newly created Session object? When and where should I create the session object? I am thinking as a property of the container object? Or should the container object be created as a property of the session object?

Again, I haven't attemped anything yet. I just thought I would put it out there to see if others have done anything similar. Any suggestions would greatly appreciated.

Thanks,
Bill