Well, just because they are named the same doesn't mean they are
the same. I shudder to think how many tables I've seen where the primary key is named 'ID' and they have nothing to do with one another.
And it is more than reasonable that a foreign key constraint column could be named one thing in one table and quite another in the other table.
And even if the columns are referring to the same entity, it does not necessarily follow that you'd want the referential constraint always defined.
Such assumptions as you wish Enterprise Manager would make seem to me to potentially cause more trouble than they are worth, but that's just my opinion. In any case, EM doesn't do that. You have to define the foreign key relationships explicitly.
Custom Apps, Inc.