>There are some sneaky places where field or variable references could be hiding:
>- in the group definitions
>- in the report variables
>- in field expressions and printwhen area
>
>I would suggest getting to the bottom of these error. I encounter them sometimes but they are always the result of a reference that has not been removed. I would suggest the following. Create a new report then cut and paste each control over to the new report. After each paste run the new report until the error is encountered. Voila. Depending on the report it could be lots of work.

A more interactive approach is to run the report preview from the report designer - any error which occurs there, calls up the appropriate dialog for setting the offending object. Just make sure to preview to the last page - the error may come up in the summary band...

One more thing which I don't know is how would called expressions (usually UDFs) which are reevaluated on entry into a band or on exit (i.e. band header/footer) show up if they errored out. I guess it would call the editor with offending code highlighted, or just "procedure cancelled".