Have you checked the forms to see if some object (particularly a dropdown or list) references case.CaseNo?

>The error message indicates a structure issue; it seemed prudent to focus on that.
>
>If it were a structural issue, wouldn't it happen all the time and not just when the change in PK is cascaded to the child tables?
>
>What were the original and changed PKs? Does it fail for only a specific change or all PK changes?
>
>The RI routine works just fine. It is after the RI code runs that the problem occurs. And it only occurs when using local views. The problem does not occur when using remote views
>
>Does changing the PK back to original value "fix" the problem or stay broken?
>
>I can't do that. After the PK is changed and cascaded to the child tables everything is broken. It can't even find the column caseno in the parent view.
>
>Are you running into an accidental keyword, wildcard or end of file?
>
>No - this table used to be named case - I changed it to FuneralCase.
>
>Is tracing the RI code during the update possible?
>
>I have traced through the RI code and it runs just fine.
>
>What is in the additional aliases?
>
>It is empty. This form is the parent of a bunch of related child forms.
>
>Thanks for sticking with me. How long have you used VPM?