Liveware Publishing Support Forum

I have a header detail relationship set up. I am attempting to print out the header info, then list all the associated details from the three detail tables. I have the files setup (set to scan) but I can only get one of the detail tables to properly report. The goal would be to print some of the header fields, followed by details from detail_table1, then details from detail_table2, etc. The end the report with the remaining fields from the header table. Are there any tricks I should be doing? I seems I can manage this behavior with only one of the detail tables, and even that I have to setup group headers and footers for the main header table and report the detail table on the "record" band only. What do you think?____Frank (fcostello@infornet.com)____Oh i have version 10.0__

You have a multiple scan report where a parent file has two scanned children. I will send you a report via email that will give you an example of working with this kind of report structure.____Kathleen__R&R Support

Fantastic! I can^t wait to take a look at it... I^m racking my brains over here..____Frank __(loyal user since the DOS based version!)__

Kathleen,__I^m interested for your example, can you send me too please__guy.gasiorowski@online.fr__thanks____>You have a multiple scan report where a parent file has two __>scanned children. I will send you a report via email that __>will give you an example of working with this kind of report __>structure. __>__>Kathleen __>R&R Support __

I just send the files out to you.____Kathleen__R&R Support

ok Kathleen,__I tested but the scan function doesn^t exist in sql version.__How to do scan function in sql version ?__Guy

In the SQL version you need to create a User SQL report that unions two separate select statements.____This is a reasonably complex kind of report to do...____Kathleen__R&R Support

arghh Kathleen, it^s always more hard in sql.__It^s not good for me__

to avoid the SQL complexity i have solved the problem you are talking about by using RR-SQL to EXPORT the master table to a DBF and then each child selection to a DBF - then using RR for xbase to build the actual report. It^s a lot easier than doing a hand-crafted UNION in SQL. ____you wind up with (1) several simple RR-SQL reports that only do EXPORTS to DBF files (2) use Visual Foxpro to create the needed index (CDX) files for the child dbf files (or you can use the RR indexing flexlink option) and (3) create a simple RR report that processes the data now in DBF files. - it^s a LOT easier than using SQL.____good luck,__nick______

He thank you Nick but i used dbf version but now i use sql version. I bought this version specially to work with sql server 2000 and now i must re-use dbf. It^s not cool, i think.__May be a patch to correct all of samlls disagrements ?__