I have a non transactional object (A) that uses another helper object (B) 
to organize some user input. (B) basically collects what the user 
requested and stores in it an internal collection. I use a mthd call 
(A.AddVal()) through (A) so that the Client does not have to instantiate 
the (B) object. After I call this method any number of times in (A) I then 
call another method (A.Organize) that uses the collection stored in (B) 
and does its own thing with it. 

I know I could have encapsulated the (B) logic in with the (A) object but 
the (B) object will be used to support other objects down the line 
depending on their need. So it will be seperate.

I have read a few articles on the subject (Ted Pattison "Basic Instincts"; 
Don Box "Q&A ActiveX/Com") and many books on COM and Com+( too many to 
list) but I still get confused as to when state is acceptable. My thought 
was with non transactional Com objects State survives when Com+ host the 
object.

If anyone has thoughts or a good rule of thumb or just some plain and 
simple clarity then please let me know directly or via this thread. 

Thanks in advance...