
	 gt; button and the search will start.<BR><BR><B>3. Navigator tree disappears</B><BR>Sometimes
	 when you are in a tree-style interface (navigator, security manager, graphics manager,
	 object browser) refreshing multiple times using the {requery.gif, ALT="Refresh"} symbol might cause
	 a javascript error with the consequence that the tree will disappear. Just close
	 the window or go to home and restart the component.<BR><BR><B>4. When using Internet
	 Explorer the User Interface does not behave correctly</B><BR>There have been reported
	 some small issues when using IE 5.5. Sometimes graphics are not displayed correctly.
	 Refresh the pages and most of the time the graphic will be there. <BR>Sometimes
	 windows are not centered correctly. Just move the window to the center and you are
	 able to close or enlarge it.<BR>If you use the back button in IE you might find
	 that you get a java script error in the different trees. Just close the window and
	 restart the ROB component you were working in.<BR><BR><B>5. When I do check in
	 through the Repository Navigator I get an error</B><BR>This error might be caused
	 because someone else is performing an action in the same folder or with the same
	 file in another session and you have not refreshed your screen. Just refresh your
	 screen by using the {requery.gif, ALT="Refresh"} symbol. Best is to at least requery the parent
	 folder or workarea. If this does not work leave ROB close your internet browser
	 and start ROB again.<BR><BR><B>6. The tree in the Repository Navigator is not properly
	 refreshed</B><BR>After specific operations from the right pane of the navigator,
	 such as File Upload, Check Out/Check In/Undo Check Out Folder, Create Folder, the
	 navigator tree may not reflect the new situation properly, since it was not refreshed
	 by the tool. Refreshing the navigator tree is never done automatically and is always
	 a user action. Note that refreshing a node effectively means: refreshing all children
	 of that node, but not the node itself. A common problem is where the folder that
	 is selected in the tree was checked out in the right hand pane. If the tree is not
	 refreshed, it will show the version that is not checked out and that is no longer
	 in the workarea. Selecting this version will lead to an erroneous situation. The
	 workaround here is to select (in the tree) the parent folder or the workarea and
	 then refresh by clicking on the {requery.gif, ALT="Refresh"} requery icon.<BR><BR>
	