dangerous reference of an ambiguous view variable

When you have the define data:
1 v1 view of xyz
2 field1
1 v2 view of xyz
2 field1
and you have several gets of v1 and v2 you can use field1 in Program.
The Compiler refers to the last get that is made, not in Program flow, but in Sourcecode lines.
this is dangerous because introducing of copycodes can lead to unexpected missreferencing of variables.
We´d like a possibility to forbid ambiguous view referencing.