<!DOCTYPE html
  PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<!--
Copyright (c) 2006 UGS Corp.

All Rights Reserved.

This software and related documentation are proprietary to UGS Corp.
-->
<html>
   <head>
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <title>Results Viewing - Load Comply Errors</title>
      <script language="javaScript">
        abridged="false";
        displayConditions=new Array();
      </script>
      <link type="text/css" href="../css/main_styles.css" rel="stylesheet">
   </head>
   <body class="bodydocs" onload="top.pageLoader()" bgcolor="#FFFFFF">
      <div class="title_topic4" id="xps10_pagetitle">Results Viewing - Load Comply Errors</div>
      <hr noshade="true">
      <table cellspacing="4" width="100%" align="center">
         <tr valign="top">
            <td bgcolor="#f4f4f4" colspan="1" rowspan="1" width="20%">
               <p class="para_td"> <a class="links" href="javascript:void(0)" onclick="top.openFile('nx_analysis/vda_checker.html');return(false);">Check VDA-4955 Compliance Overview</a></p>
            </td>
            <td bgcolor="#f4f4f4" colspan="1" rowspan="1" width="20%">
               <p class="para_td"> <a class="links" href="javascript:void(0)" onclick="top.openFile('nx_analysis/vda_results.html');return(false);">Results Viewing</a></p>
            </td>
            <td bgcolor="#f4f4f4" colspan="1" rowspan="1" width="20%">
               <p class="para_td">Load Comply Errors</p>
            </td>
            <td bgcolor="#ffffff" colspan="1" rowspan="1" width="20%"></td>
            <td bgcolor="#ffffff" colspan="1" rowspan="1" width="20%"></td>
         </tr>
      </table><br><p class="para_topic">When you select Load Comply Errors from the VDA Checker dialog, the dialog disappears, and the Load Comply Error Objects dialog appears to restore comply errors.</p>
      <p class="para_topic">All violations found are stored as comply errors in an external &lt;partname&gt;.ceo file (Comply Error Objects File) if the VDA Checker has finished an analysis run.</p>
      <p class="para_topic">A comply error entry number maintains information about the violation condition for error tracking purposes. Comply errors are organized into a separate list for each check criterion.</p>
      <p class="para_topic">Object identification in NX works with tags (object_id, number). The tags are used by the Browse Violations dialog to identify and highlight objects that cause violations. A tag uniquely identifies an object in an NX session. In contrast, the *.ceo file contains information of NX handles that are session independent and can be mapped back to object identifiers (tag) in another session. This mapping is carried out inside the VDA Checker every time a *.ceo file is read in.</p>
      <p class="para_topic">A file selection dialog is used to restore comply errors from a Comply Error Objects File, which was saved after a previous analysis run or was created at the end of a UF_MODL_ask_vda_4955_compliance user function call. </p>
      <p class="para_topic">The file also contains the corresponding results log, which is copied to the Results Log report. After restoring the comply errors, you can view them using the Display Results Log or Browse Violations options. </p>
      <table border="0">
         <tr>
            <td valign="top" align="left"><img align="left" src="../graphics/note.gif" alt="Note" title="Note"></td>
            <td valign="bottom" align="left" width="100%">
               <div class="para_note">
                  <p class="para_note_body">The usage of the restored comply errors is restricted to these two functions and has no influence on current VDA Checker settings. The next analysis run will delete all comply errors and report new ones (if any). </p>
               </div>
            </td>
         </tr>
      </table>
   </body>
</html>