Foreign Keys damaged

[Atomic Flounder]

Hello,

I have the following problem.
I created a data model as described in the chapter "Database Engineering" of the EA User Guide.
Today I realized that all my FK constraints are damaged.
The associations are still in the diagrams and the FK operations are also still in the classes.
But the problem becomes obvious in the "Foreign Key Constraint" dialog (right click on an association -> "Foreign Keys...").
In the column lists at the bottom of the dialog, in all cases one or both of the involved columns have vanished.
I once renamed some of the FK constraints. And something seems to have gone wrong because at the FK ends of the associations there are still the old names. However the problem also affects FK constraints which have not been renamed. I also could not reproduce the behaviour.

Do you have an idea what could have happened? A colleague told me that she had the same issue, but also could not find out the reason.

In all tables' properties dialogs I chose "Oracle" as database.
I'm using Enterprise Architect 9.0.908.

I also have another Question:
When one renames a column which is involved in a FK constraint this message is shown:
"Columm <Column> is part of a foreign key relationship. Do you wish to propagate the change to connected tables?"
Although this does not seem to affect my problem (i tried both answers in a test project and in both cases my FK constraints stayed intact) I wonder what exactly EA does when I choose "yes". I did not find anything about this topic in the user guide.

Regards
AF

[valico1]

Hello,

unfortunately we have the same problem in version 7.5. Is this bug improved in new version 9.3? Do you know about some workaround?

Regards
Ondrej

Hello,

I have the following problem.
I created a data model as described in the chapter "Database Engineering" of the EA User Guide.
Today I realized that all my FK constraints are damaged.
The associations are still in the diagrams and the FK operations are also still in the classes.
But the problem becomes obvious in the "Foreign Key Constraint" dialog (right click on an association -> "Foreign Keys...").
In the column lists at the bottom of the dialog, in all cases one or both of the involved columns have vanished.
I once renamed some of the FK constraints. And something seems to have gone wrong because at the FK ends of the associations there are still the old names. However the problem also affects FK constraints which have not been renamed. I also could not reproduce the behaviour.

Do you have an idea what could have happened? A colleague told me that she had the same issue, but also could not find out the reason.

In all tables' properties dialogs I chose "Oracle" as database.
I'm using Enterprise Architect 9.0.908.

I also have another Question:
When one renames a column which is involved in a FK constraint this message is shown:
"Columm <Column> is part of a foreign key relationship. Do you wish to propagate the change to connected tables?"
Although this does not seem to affect my problem (i tried both answers in a test project and in both cases my FK constraints stayed intact) I wonder what exactly EA does when I choose "yes". I did not find anything about this topic in the user guide.

Regards
AF

[ChristiaanK]

EA 9.2.922 here. I experience similar problems. Had all my foreign keys defined, and they were ok. I change something to one of the tables (a field/column that is not part of a FK relationship): the FK-marker in the table is gone, and the Foreign Key in the project browser is gone. The association is still in the diagram, still showing the requested label (columnA = columnB).