Well, what we are finding is that if you need to pass large amounts of data between objects then it's likely you can combine those into the one class - ie the class design is a little suspect.
You can also run forms from a session class and that form will see the session's data.

We find XML fast for anything but huge data sets, but like you I find that annoying in a data language that should allow you to deal with cursors.

For example if I have a stock control module and an address module I should be able to return a cursor of addresses for my stock locations for use in the stock module. (purely hypothetical here!) We don't have a solution to that sort of problem other than XML. Which is why I'd simply love a

select ... into cursor ... datasessionid x

type syntax. But I don't think we'll ever see it, even though I repeatedly here developers wanting to do things that would be facilitated by something like this.




>
>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 ?