The iiimport command copies application components from an intermediate file into an existing application. The intermediate file, created by iiexport, contains the definitions for the components you specified when you ran iiexport. See the description of iiexport for the types of components you can copy.

When you import a component, the iiimport command assumes that the component exists in the application, and revises the existing version of the component. When you import a frame, the existing frame definition, including local components and Escape code, is replaced with the new definition. The iiimport command does not change menu items for a frame, except for user-defined menu items included with Escape code. See How Dependencies Are Handled for information on how iiimport handles menu items and other dependent components.

You can check whether a component exists in the target application by using the -check option. Running iiimport with the -check flag does not actually copy or replace any components, but reports on the status of the components in the target application.

If a Vision frame does not exist in the target application, iiimport copies the frame but does not incorporate the frame into the Application Flow Diagram. From the Application Flow Diagram, you can use the Insert option to include the frame at the desired location.

You can import a component that does not exist in the target application, but the target application itself must exist. To copy an entire application into a database, use the copyapp utility.

All components copied in are assigned to the owner of the target application.

This command has the following format: