Why not make transaction a type - and report a property. The property would be of type Foo, which is one of the three type reports. Don't forget that a CFC property can also be a CFC itself.
-ray > > Here's the tricky part (for me). Each of these three reports could be > applied to 4 different types of transactions...One kind is an > authorization > another is a credit etc.. > > So...I'm torn between extending each report TYPE to have a > sub-classes of > auth,settle,credit and failed OR having AUTH,SETTLE,CREDIT and FAILED > objects which are then extended based on the type of report it is... > > Report Object -> Report Type -> Transaction Type > > Or > > Report Object -> Transaction Type -> Report Type > > Going forward I'm sure there will be additional report types > but very rarely > would there be additional transaction types added to the equation. > ______________________________________________________________________ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
