Steve, Another thing occurred to me... I think I remember a case where (I think because I renamed a table or relationship) a calculation or layout ended up being in a context that I hadn't intended, and maybe that threw a 106 error. Maybe recheck both the layout and fields for the same context? -Troy