>...Again the report would still hang for certain records.
>
>Now the report in question did have function calls in some of the field expressions. I tried creating a new version of the report without any expressions or function calls at all and this cleared the problem in testing.
>
>After a few days of trying to trouble and resolving to re-write the report and just do all the expression formatting and function calls in the query leading up to the report call, the problem just dissapeared. All of a sudden every data record was printing fine. Other problems in the system seemed to be resolved too.
>
>Now to verify our assumption that the issue was data related, we had the data restored from a day when we knew it was bad, and sure enough we could reproduce the problem with that data set. We looked at that data set and saw no obvious corruption or funny characters.

My Hindbrain keeps suggesting that it is a pathing issue with the back-then not prerun function calls, although my forebrain tells me that this is inconsistent with my interpretation of the last part <bg>.

If Al's hints don't shed any light, try to find the offending records by running a batch of those reports priinting into files, but only for one "leading record". If you find a culprit record, do the same for the 1:n:m records involved... Working off an ID-cursor for the leadihg records this should not be difficult to implement...

HTH

thomas