>I get 2 cursors from a SQL pass-through. I have set a relation between these two tables.
>It happens that for an over 3500 records from the parent table I have a few (6) printouts without name and address (the name and address is from the child table).
>It looks that the relation was broken for these 6 printouts - this happened 2 weeks ago.
>Today I restored the same database and I run the same exe to verify again what happened and to find an explanation to this. Now it printed the names and addresses on the 6 ones that 2 weeks ago didn't have any names and addresses, and it didn't print names and addresses on other 6.
>Is there any unusual thing that I don't know about "set relation"? Could anybody give me some answers?

While it does not address your question, one workaround might be to use a SELECT - SQL statement to create a single cursor out of your two source cursors, to be used to drive the report. It would avoid the need to SET RELATION and allows you to JOIN, set WHERE filter clause(s) and ORDER BY in any manner you choose.

You can also eliminate duplicate records and/or SCAN the result cursor for blank column(s) prior to running your report.