@mkeintz wrote:
@Astounding's suggestion is good for the current situation, assuming no department currently has two people with the same name.
But people change departments - and much less frequently they change names. Either the identifier will remain fixed, but lose informational value (so why use name & dept to begin with?) - or it will be modified to follow the employee's changes, requiring a table of links between old and new identifiers.
There will be blood.
Sounds like you may have bitten by the same things that I have. Including the "new database implementation will use new identifiers" headache.
... View more