>>>I like the session class, which has to be created in a prg. The private datasession option then allows you to isolate your tables from the rest of your app in a secure way. We've found since switching to this kind oa scheme that our errors and data reliability has improved dramatically.
>>
>>Just intereted to know, how do you pass data between your objects when they all have private datasessions ?
>
>Really good question! We try to get each module to do as much work as possible internally, ie quite a few tables are opened many times in different sessions. Doesn't seem to be any performance issue. Where we do need to pass data we either pass in the datasessionid or use XML. I asked Ken Levy about possibility of doing something like
>Select * from mytable into cursor mycursor datasessionid x
>but he couldn't see the justification at the time.

I currently use business objects that use the default datasession. The reason is that I often have objects ask other objects for datasets and it seems like a lot of (slow) mucking around to pass data between the objects.

For example - if I have a form that handles a shift for a department and needs a cursor with emplyees and a cursor with the shift record etc. - I would get the list of employees from my employee business object and my shift record from my shift business object.

Are you saying that you would get everything from the one object ? If not, how do you handle this sort of scenario ?