The suggestion to allow variant access points based on the same (preferred) name has the character of a "quick fix". Things do need fixing. Here's a scenario.
Consider the situation where a name is established with a qualifier other than the year of birth, it not being known to the cataloger. Then another cataloger discovers the birth date and includes a see reference using it. That reference serves as a place marker to prevent a subsequent namesake born in the same year from being established in that way.
First cataloger establishes:
100 Bloggs, Fred $q (person with no known qualities)
Second cataloger finds out that this person is born in 2016 and adds:
046 $f 2016
400 Bloggs, Fred, $d 2016-
Third cataloger works with another namesake also born in 2016. The cataloger now is prevented from using Bloggs, Fred, $d 2016- because it conflicts with the existing AAP.
Addition of field 400 doesn't "solve" the problem, but it at least prevents the third cataloger from compounding the confusion. Instead, the namesake might get:
100 Bloggs, Fred $q (person with at least one known quality), $d 2016-
Sincerely - Ian
Cataloging and Metadata Services Librarian
George Mason University
[log in to unmask]