Nor should you be storing calculated data (reminder days) if that's what is meant by Renual(sp?)Date.
Unless you have a good reason to do what you're doing, I agree with the normalization suggestion. As I see it, a contract is an entity that has attributes (characteristics) and you shouldn't repeat records of an entity. Rather than have a record for each renewal, why not just a renewal date? I see nothing in the fields that suggests there is a reason to have a separate set of records that would make them unique (such as who handled the renewal).
Assuming the renewal field is how many days before getting a reminder, then what about
ContractIDpk |
ContractNum |
StartDate |
EndDate |
RenewDate |
RenewDays |
1 |
ABC123 |
4/01/19 |
3/31/20 |
|
30 |
where RenewDate is Null because it was never renewed. When it gets renewed, you update that field each time.
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.