When the Database Reverse Engineering tool is executed within the GeneXus IDE; some extra checking are done in the current Knowledge Base regarding the physical model (Tables, Data view, Attributes, Indices and so on).
When selecting a Table, DBRet will check if the table has a Data View in the current KB and was not selected in the DBRet Wizard Step #2 and is related to the selection.
For example, if it is referenced in the selection extended table as Foreign Key.
There is an existing Data view in the current Knowledge Base; the user selected again the same table to be imported.
The selected database table does not have a Primary Key; the user will need to select a Primary Key to be imported in the KB.
The attributes detailed in {0} were chosen as primary key as there is a unique index containing them.
The selected attribute is autonumber.
Table {1} was not selected in the table list.
The selected Index partially contains the selected attributes.
Indices with the same composition are ignored.
Indices with attributes without Name or Key are discarded.
The selected index is Primary Key and not duplicate.
The selected attribute type is not supported.