>A couple of the reports have UDFs in the fields. I've seen the C5s in reports with and without....but are you thinking there may be something hanging around from a previously run report? Do you have a suggestion of something I should be looking for?
>
>The problem has existed for awhile. It's taken some time for it to get to the top of the priority list. To tell the truth, I started working on it before Christmas when I anticipated that I was going to have a few weeks of interruptions and distractions. I figured I could try things as they occurred to me and I could fit them in when I had a half hour or a half day. By now, though, I've really got my stubborn up. I'll be damned if some stupid reports are going to get the best of me! <vbg>

Further suggestions from out in left field < g > :

- Re: your UDFs - are they complex? Do the reports take long to run? Do the UDFs change the work area without changing it back when they're done?

- do you pre-build report cursor(s) or do you use a report DE with tables and/or views?

- if you're seeing the problem with non-UDF reports, maybe you could call a "dummy" function at the end of each report (e.g. in Summary band) that calls SYS(1104) - or call after your REPORT FORM ...

- with earlier versions of Fox there were issues if you called a report while a Grid has focus; if you're doing that you might try .SetFocus() to something else before running the reports.

- looking at things globally: is there ANY non-VFP software running on the problem systems? Either other complete processes, or ActiveX within VFP? I think most of the common causes of printing-related C5s have already been offered in this thread and AFAIK such problems are not common in VFP7. If you're seeing a lot of them I'd tend to think there's something different about your environment.

I assume you're seeing these problems on a variety of hardware. If it was a monoculture I'd suggest upgrading video drivers.