I have been handed a Access 97 db that I figure was overdesigned. My problem is that the employee table has relationships with other tables with referential integrity being enforced. BUT the designer did not set up cascading updating. I can understand that cascading deleting will cause problems but no update?
The primary key is an employee ID# which this being a typical company is impossible to get from HR. Therefore the people who have been using it have been making up ID#s when necessary. Now we would like to link this to our employee table which has correct data and info in it.
However the constraints prevent us updating the employee ID#.
I discussed this with the designer and his opinion was that if I changed the relationship to allow cascading updates it would break the db relationships.
Is he being over cautious, am I being under cautious to consider this?
If you have dealt with a similar problem I would appreciate your input.
The primary key is an employee ID# which this being a typical company is impossible to get from HR. Therefore the people who have been using it have been making up ID#s when necessary. Now we would like to link this to our employee table which has correct data and info in it.
However the constraints prevent us updating the employee ID#.
I discussed this with the designer and his opinion was that if I changed the relationship to allow cascading updates it would break the db relationships.
Is he being over cautious, am I being under cautious to consider this?
If you have dealt with a similar problem I would appreciate your input.