Abstract: A copy of a new version of an existing Envy Library file is transferred to a data processing system in which the existing Envy Library file is stored, such that the amount of data actually stored is smaller than the data contained within the new version of the existing Envy Library file. Scripts containing information about unchanged data that can be copied from the existing Envy Library file is stored in the data processing system. Scripts containing information about data in the new version of the existing Envy Library file that is different from data within the existing Envy Library file is also stored in the data processing system. The existing Envy Library file may be regenerated using the script files and the new version of the Envy Library file within the data processing system.

Abstract: A bridge for exporting and importing Envy components to and from a TeamConnection object oriented programming environment includes an Envy side and a TeamConnection side. The Envy side of the bridge creates and transfers an Envy library file that contains the contents of a selected Envy component and a Bill of Materials that describes the contents of the Envy Library file. The TeamConnection side of the bridge searches the transferred Bill of Materials for keywords associated with objects. The TeamConnection side of the bridge then creates a TeamConnection part for each object identified by a respective keyword. To import an Envy component stored within a TeamConnection object oriented programming environment, the TeamConnection side of the bridge creates and transfers an Envy library file containing the contents of the Envy component and a Bill of Materials describing the contents of the Envy library file. The Envy side of the bridge searches the Bill of Materials for keywords.