
	The Repository Object Browser will also display {dependancy_manager.gif, ALT="Dependency manager"}
	 Dependency data for objects, if those objects have been parsed (from either the
	 Command Line Tool (da command) or the Dependency Manager. The Dependency data displayed
	 consists of three parts:<BR><BR>* {property_pallette.gif, ALT="Property pallette"}Details - all secondary
	 elements recognized by the Dependency Parser. For example a Java File typically
	 will contain Class Definitions or a Package create script will contain PL/SQL Routines.
	 For each detail, the Browser will list all usages made of it. So for example the
	 PL/SQL Routine found in a Package will list all the objects that make a call to
	 this routine.<BR>* {uses.gif, ALT="Uses"} Uses - all usages made of other elements by the object
	 under scrutiny. Here you will find for example all tables and columns used by a
	 Form, a Package or a SQL script. And all PL/SQL routines called by those objects.
	 For all usages, the property palette displays all (parsed) objects that provide
	 the detail that is the object of this usage.<BR>* {usedby.gif, ALT="Used by"} Used By - all usages
	 made of this element by other elements are listed.<BR><BR>Note that you have to
	 parse objects for dependencies yourself in order to have the Repository Object Browser
	 display any dependencies. Also note that you will only see usages of an element
	 by other elements that have been parsed. It cannot decisively be concluded that
	 an object has no impact (and can therefore freely be changed) if the {usedby.gif, ALT="Used by"}
	 Used By-node lists no usages. It simply indicates that no objects have been parsed
	 that make use of this object. But there may be many objects, still to be parsed,
	 that also make use of the object.
	