
	With the basic search you can search on name, element type, work area or folder.<BR><BR><B>Name</B><BR>The 
	 name search is case insensitive and you can use_ ,  % or * as wildcards e.g. customer%
	 to get all objects whose name start with customer. Or *.fm_ to find all objects
	 with an extension that starts with <i>fm</i> and has one additional character. If
	 you want to search case sensitive check the check box behind name. Note that a case
	 sensitive search is faster than a case-insensitive.<BR><BR><B>Tip latest</B><BR>Tip
	 latests means that only the latest version will be shown for each branch. If you
	 want to see all versions uncheck this checkbox<BR><BR><B>Include Nested Folders</B><BR>If
	 you check this checkbox the search will not only look in the given folder but also
	 in all of its subfolders. Depending of the number of subfolders this query may take
	 longer to very long.<BR><BR>As an alternative to checking this check-box (which
	 instructs the search tool to traverse the entire nested folder structure and results
	 in a rather nasty execution plan) you can make use of an additional where-clause
	 (see the Advanced search options). Instead of explicitly walking through the folder-tree,
	 we can instruct the search tool to only return objects whose Folder-path is LIKE
	 a certain value. The where-clause required for this:<BR><pre> jr_name.get_path(e.ivid,'NAME','/',0)
	 like 'Folderpath/%' </pre><BR>If for example we want to look for all objects in
	 the <B>HRM/oracle/....</B> folder tree, instead of selecting the HRM/oracle folder
	 and checking the <i>include nested</i> check box, we could add the additional where
	 clause:<BR><pre> jr_name.get_path(e.ivid,'NAME','/',0) like 'HRM/oracle/%'
	 </pre><BR>and the result would be the same. This second approach in most cases seems
	 to render a result much faster than the first (included nested), especially when
	 there are additional search criteria (such as name, type).
	