Make life easier. Select all the data into one cursor for the report. No need to worry about relations and if someone hits the "print" button in preview.

>Does this make sense to anyone? A report has a field which is obtained via a lookup to a table other than the one that's driving the report; however, if the driving table has a relation set into yet a third table, VFP generates an "Index tag not found" error (absolutely not the case) when the lookup is attempted (but only if the report is for a scope of more than 1 record!). It doesn't matter if the lookup is done in a procedure-file function or in an IIF in the report. If I remove the relationship, the lookup works fine. I got around it simply by setting a relation into the lookup table, but -- does this sound familiar to anyone? (Of course, it took me a good portion of two days to figure out what was happening...aarrrggghhh....)