Hi guys, I would like to know the technique for modelling classes that appear in Reports and summary views etc. Very often the requirement at the client side is to present some sort of a hybrid structure. Example, in a order entry system, we may have OrderHeader and OrderDetail objects (never mind the names), The OrderDetail we just be storing the ItemID, but when ever the contract form is printed, we may need to display more than just the cryptic ID of the item. Similar situations can arise when ever we are supposed to print reports, summary etc. In these sort of situations what is the best OO practice? DO we need to have a differenct class for each of these situations or what? Thanks Pankaj ************************************************************************ * Rose Forum is a public venue for ideas and discussions. * For technical support, visit http://www.rational.com/support * * Admin.Subscription Requests: [EMAIL PROTECTED] * Archive of messages: http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl * Other Requests: [EMAIL PROTECTED] * * To unsubscribe from the list, please send email * * To: [EMAIL PROTECTED] * Subject:<BLANK> * Body: unsubscribe rose_forum * *************************************************************************
