Novell ADMINSTUDIO 9.5 User Manual page 1151

3. In the Component's Property grid, change the value in the Component Code field to match the Component
Code (ComponentId) of the component in the other project.
If it is unclear what the value should be changed to, follow these steps:
a. Open up the package that will not be modified in Direct Edit mode by selecting Open on the File menu,
and then selecting Direct Editor under Additional Tools. A list of the package tables is displayed.
b. Select the Component table and search for the Component Name displayed in the conflict.
c. Once the entry is found, take note of the value displayed under the ComponentId column. This is the
Component Code that should be used for the component in the other package.
4. Select Save As on the File menu and save the changes as a Windows Installer Transform (.mst) file.
5. Open ConflictSolver and reimport this package with its newly created transform file into your Application
Catalog, and then use the Conflict Wizard to check it against ACE14 again.
ACE15
ACE15 checks for the existence of identical ODBC entries in components with different ComponentIds. The ACE15
Error String is displayed in the following format:
The ODBC entry [ODBC_ENTRY] in the component [COMPONENT1] in the package [PACKAGE1] conflicts with
the same ODBC entry in the component [COMPONENT1] in the package [PACKAGE2].
Summary
Table 13-27 • ACE15 Summary
Topic
Conflict Type:
Description:
Result:
Resolution Type:
Resolution:
AdminStudio 9.5 User Guide
Chapter 13: Identifying and Resolving Application Conflicts Using ConflictSolver
Description
Conflict Rule / ODBC Resources
Checks for the existence of identical ODBC entries in components with different
ComponentIds.
If identical ODBC entries exist in components with different ComponentIds, ACE15 fails.
Automatic (CARD15)
ConflictSolver changes the Source ComponentId to match the Target ComponentId.
ADS-0950-UG00
Application Conflict Evaluators (ACEs)
1151