>>Wow. Is there a reason this field is in multiple tables?
Sounds like a foreign key from an editable primary key. I agree it's not ideal to use an editable primary key, but since he inherited it:
My answer would be that this is very easy in SQL Server, but assuming it's a foreign key field in DBC tables: a CASE tool like xCase should make it very easy to identify the usage of this field including referential integrity. Also makes it easy to maintain/grok large unfamiliar databases going forward.
"... They ne'er cared for us
yet: suffer us to famish, and their store-houses
crammed with grain; make edicts for usury, to
support usurers; repeal daily any wholesome act
established against the rich, and provide more
piercing statutes daily, to chain up and restrain
the poor. If the wars eat us not up, they will; and
there's all the love they bear us."
-- Shakespeare: Coriolanus, Act 1, scene 1
