
	Reports are as condensed as possible: For each element type, the report contains 
	 only properties that have a value and lists of details if they exist. The layout
	 is styled after the Oracle Method and CDM Manuals. The reports are laid out in 
	 such a way that printing them renders very acceptable results.<BR><BR>Element definitions
	 in Designer are characterized not just by their own properties but usually to a
	 large extent by their references to and dependencies on other objects. For example
	 an entity and its relationships, a business function and its data usages and event
	 triggers and of course tables with their foreign keys and associated data logic
	 as well as modules with data usages, module network and associated business rules.
	 ROB reports leverage the browser hyperlink functionality by providing hyperlinks
	 for each object reference and dependency displayed in the ROB reports. By simply
	 clicking on associated elements in the report, the user can easily navigate through
	 complex dependency structures. For example from Module to Table to underlying Entity
	 to associated Domain and back.<BR><BR>Note: references to other objects potentially
	 refer to objects in another folder or application system than the one owning the
	 object that is the focus of the current report. You are only allowed to actually
	 navigate to objects that are owned by containers (folder/application system) that
	 you have access to. If that is not the case, instead of a hyperlink, you will see
	 the name of the referenced object followed by the {noacc.gif, ALT="No access"} icon, with an ALT
	 text stating: <i>Object is owned by a Folder on which USER has no access privileges.</i>.
	 <BR><B>Also See</B>
	 <BR><A href="javascript:parent.showHelp(1710)">What is CDM?</A>. 
	