Multi scan prob (R&R Win 8.1.023)

Meeting place for R&R customers and clients to share tips and ideas. Post your questions, messages or problems here.
Post Reply
Gene_Clark
Posts: 10
Joined: Tue Oct 10, 2017 12:44 pm

Multi scan prob (R&R Win 8.1.023)

Post by Gene_Clark » Wed Feb 27, 2002 9:40 pm

I am developing a report for which I need multiple, nested scanning, including 3 scans of the same FOX PRO dbf pair. Every thing runs fine for 1 nested (scan related to another scanned dbf) of one dbf and 2 nested scans of the same (different from the above one) dbf. When I relate another nested scan, I get no indication of any problem, except that I get no output for the last nested scan.____In fact, I replace the third nesting of the same dbf with a non-nested scan of a third dbf, and could get no output from that scan.____Is there a limit to the no. of relationships I can set up? I now have ten relations, of which 8 are scans (3 are scans of other scans) and 2 are lookup. It looks like 9&10 are not working.__

kfleming
Posts: 5795
Joined: Tue Oct 10, 2017 12:44 pm

=> Multi scan prob (R&R Win 8.1.023)

Post by kfleming » Thu Feb 28, 2002 7:43 am

The relationship limit is 99.____Have you done a test report using the same parent/child that is giving you the problem to make sure that it works correctly?______Kathleen__R&R Support

kfleming
Posts: 5795
Joined: Tue Oct 10, 2017 12:44 pm

=> RE: Multi scan prob

Post by kfleming » Thu Feb 28, 2002 7:44 am

Okay, I figured it out. Me, the novice. Apparently, if you have a QUERY condition set, you MUST have some type of query condition set for all DBFs being scanned, even if you want all records in the scanned DBF to be used. Is that right?____I added a section to the query to take all records, and that seems to work.

Gene_Clark
Posts: 10
Joined: Tue Oct 10, 2017 12:44 pm

==> Multi scan prob (R&R Win 8.1.023)

Post by Gene_Clark » Mon Mar 04, 2002 1:44 pm

That is true because in a multiscan each composite record will have values from only one child table.____So if I am scanning charges and payments____CUST CHG->DATE PAY->DATE__123 01/01/2002__123 01/15/2002__456 01/10/2002__456 01/12/2002____A query for CHG->DATE ={01/*/2002} will never be met by any of the payment records and you would only see the first and third records.__But having CHG->DATE ={01/*/2002} or PAY->DATE ={01/*/2002}__would select all 4 of the records above.____Kathleen__R&R Support

kfleming
Posts: 5795
Joined: Tue Oct 10, 2017 12:44 pm

===> Multi scan prob (R&R Win 8.1.023)

Post by kfleming » Mon Mar 04, 2002 2:20 pm

The forum software compresses all vertical spaces to a single space so my illustration looks funny.____For the 4 data lines the date in record 1 and 3 belong in column 2 under charges and record 2 and 4 should be in the third payment column.______Kathleen__R&R Support

kfleming
Posts: 5795
Joined: Tue Oct 10, 2017 12:44 pm

====> Multi scan prob (R&R Win 8.1.023)

Post by kfleming » Mon Mar 04, 2002 2:22 pm

The relationship limit is 99.____Have you done a test report using the same parent/child that is giving you the problem to make sure that it works correctly?______Kathleen__R&R Support____Kathleen__R&R Support

Post Reply