just wondering if there is an easy way to id what is triggering this error when accessing a certain record? SQL 2019/2022