This function is used to carryout a global comparison of the dictionary elements between two folders. The result is given in the form of a log file where the level of detail depends on the execution options selected.

Screen management

Entry screen


The two folders to be compared are defined in this screen. By default, the current folder is proposed, but it is possible to give the name of another accessible folder, using the syntax detailed in the annex documentation.

A series of check boxes are used to select, from amongst all the elements in the dictionary, those that must be compared (with the associated code ranges).

Additionally, a filter is specified for the modules with the elements that are to be compared, as well as two supplementary questions (check boxes) :




The following fields are present on this tab :

Block number 1

  • Source folder (field DOSORG)

Define the code for the folder in which the source elements are found.

  • Destination folder (field DOSDES)

Define the code for the folder in which the search will be carried out for the elements to be compared.


  • No. (field NUMLIG)


  • Module (field MODULE)

Module belonging to the setup. This field is used to specify whether the screen has to be created in the folder database. It is specified when the module linked to the screen is active in the folder.

  • Comparison (field COPMOD)

If Yes is entered in this field, the elements of the corresponding module are taken into account in the process.

Block number 2

  • Screens (field AMK)

If this box is checked, the search includes the element type in question.

  • Windows (field AWI)


  • Objects (field AOB)


  • Object personalization (field AOC)


  • Functions (field AFC)


  • Actions (field ACT)


  • Data types (field ATY)


  • Tables (field ATB)


  • Reports (field ARP)


  • Miscellaneous tables (field ADI)


  • Messages (field AST)


  • Inquiries (field ACN)


  • Scripts (field ADC)


  • Import/export templates (field AOE)


  • Table setup/import (field AEV)


  • Classes (field ACLA)


  • Representations (field ASW)


Block number 3

These fields are used to give the start and end range for the codes to be processed.




















  • From (field ASTDEB)


  • To (field ASTFIN)




  • From (field ADCDEB)


  • To (field ADCFIN)










Block number 5

  • Det (field DETAIL)

This box is used to have a detailed log file : When this box is checked, specify the detail of the differences to log (on which field, what are the distinct values). The fact that this box is checked also adds a line signalling identical elements to the log file .

Define the language in which the comparison at the message level will be carried out. If left blank, the comparison will be carried out in all the languages.

  • Technical (field TECHNI)

If this box is checked, the technical sheet additional information is added to the log file (when it occurs the field name for the dictionary involved with the differences).

  • File (field FICHIER)
  • Format (field FORMAT)




Functions accessed by right click on the grid

Yes to all the rest

When there is an grid with multiple choice entries with a choice of response Yes / Noon each line, this function is used to respond Yes to all the lines from this line.

No to all the rest

When there is an grid with multiple choice entries with a choice of response Yes / Noon each line, this function is used to respond No to all the lines from this line.


This type of utility has a very long execution time if it is launched for the entire dictionary. It is therefore advised to limit the elements to compare and if necessary, to filter them by module.

Log file displayed in the resulting file

Shown below are examples of the messages likely to be displayed in the log file :

Line type

Log file example

Element header

Source folder : XXXX  Target folder : YYYY

Screens DD-MM-YY hh :mm


OK comparisons

XXXXXX Identical screen

nnn Identical module

Nonexistent elements

(level 1)

XXXXXXScreen does not exist under FOLDER

FFFFF Window does not exist under FOLDER

CCCC Inquiry does not exist under FOLDER

Nonexistent elements

(level 2)

XXXXX  / Field YYYY nonexistent FOLDER

CCCC /Field YYYY Difference YYYY’

Level 1 differences

Screen XXXXXX / [AMK]OPTION Grid options ‘options 1’ => ‘options 2’

Screen XXXXXX / [AMK]INTMSK Different titles ‘title 1’ => ‘title 2’

Object XXXXX  /  [AOB]TRELIS  Hierarchical list of differences ‘value 1’ => ‘value 2’

Level 2 differences

Screen XXXXX / Field YYYY / [AMZ]NUMBLOC Block number ‘value 1’ => ‘value 2’

Table XXXXX / Field YYYY / [ATZ]NOLONG Long text difference ‘text 1’ => ‘text 2’

Module nnn/ Message mmm Difference ‘message 1’ => ‘message 2’

Level 3 differences

Screen XXXXX / Field YYYY / Control Action STD / [AMA]WEBSAI ‘value 1’ => ‘value 2’

Also found in the log file is the identification of the element and its sub-elements (for example screen, field, action), as well as the name of the dictionary field in which the difference was found. The field names do not appear if the Technical tick box is not ticked.




Batch task

This function can be executed in batch mode. The standard task ACOMPOBJ can execute it.

Error messages

In addition to the generic error messages, the following messages can appear during the entry :

server : machine not accessible

The server with the name server does not respond (either because it is not accessible via the network or the service daemonadxd has not been launched).

Tables used

SEEREFERTTO Refer to documentation Implementation