Author Topic: Foreign Key to Primary Keys  (Read 922 times)

ben

  • EA Novice
  • *
  • Posts: 4
  • Karma: +0/-0
    • View Profile
Foreign Key to Primary Keys
« on: October 14, 2003, 05:22:10 pm »
It is quite common for a table to have unqiue alternate keys in addition to the primary key.  For example, an employee may have a primary key that is a system assigned numeric value.  Also, the table may have a alternate key (unique index) on another field, say Peoplesoft Id.  In EA when attempting to assign a foreign key to this alternate key in the emp table, the following message is displayed:

Target columns must match
target primary key domain.

Can this restriction be removed or overridden?

Thanks,

Ben

hd

  • EA Administrator
  • EA User
  • *****
  • Posts: 302
  • Karma: +0/-0
    • View Profile
Re: Foreign Key to Primary Keys
« Reply #1 on: October 14, 2003, 05:39:20 pm »
This restriction does not exist in the current build 647.

ben

  • EA Novice
  • *
  • Posts: 4
  • Karma: +0/-0
    • View Profile
Re: Foreign Key to Primary Keys
« Reply #2 on: October 15, 2003, 12:13:40 pm »
Thanks Henk for the the info.

I installed build 647 and tested.  Yes, the behavior has changed.  However, now EA seems to always build the link using the primary keys of the target table regardless of my having selected an alternate key from the target table.

Also, after deleting a set of related fields on the relation and then attempting to insert a new set of fields, I get the following message:

DAO.Record [3021]
No Current Record.

Thanks again.  Aside from this issue I am finding in my evaluation that EA is a great tool.  I'll be making a purchase decision soon.

Thanks,
Ben

hd

  • EA Administrator
  • EA User
  • *****
  • Posts: 302
  • Karma: +0/-0
    • View Profile
Re: Foreign Key to Primary Keys
« Reply #3 on: October 15, 2003, 03:11:59 pm »
Thanks for your comments.  :)
We are currently improving the foreign key generation feature of EA.