1. Save the package definition.
2. Check the Package. This is an optional step which will identify any errors in the current package definition, before building the package. Errors will be reported as Warning or Fatal.
This message box is shown when no errors are found.
3. Build the Package. A progress bar is displayed while the package build steps are completed. This may take some time.
The first time that a new package is built a Global Unique Identifier (GUID) is generated for the package and stored in a file. For example, folder:
4. When the build is completed, display the build log and filter for Completion messages..
5. Notice the build log dialog allows the messages to be filtered, for example by selecting Completion, Fatal or All messages only to be displayed. You search for specific entries in the log using Find.
6. Scroll down to find the copy DLLs file messages. Notice the shipped DLLs includes the four reusable parts which the main form (copy of ST_MAIN) depends upon. The DLLs for the employee file (XEMPLOYEE) and the files which it depends on due to file lookup validation rules and predetermined join fields. These DLLs are the file OAMs and should include XDEPTMENT. This is the Identifier name for the table XDepartments. The file data has also been included for these files.
You'll notice three other DLLs are included. These are reusable parts with names beginning X, which are autocomplete and dynamic picklist components associated with fields in the Employee table.
7. Check if any Fatal messages exist. Warning messages may be ignored, depending on the specific message. For example a warning which concerns an image file not found may be ignored, since the image is included in the Image object DLL which is referenced in the form or reusable part.
If fatal messages are reported you will need to review previous steps to resolve the error. For example, if a component DLL is not found it may mean components are not compiled.
8. Close the Package Build log.
9. Close the Package Maintenance dialog.