At 12:08 AM 3/16/2008, Ned Ritchie wrote:

A report FriendsList with two sub reports that uses all three tables
does not pick up on 9 of the 110 rows.

Ned,

If you don't know already, Reports, Sub-Reports and Nested Sub-Reports
in R:BASE work similar to using a multi-table form with common columns
having exact same values.

All associated tables with similar column names MUST include the same
column vales in order to meet the multi-table (similar column name)
criteria to evaluate the matching rows in a multi-table form, and now
the sub-reports and nested sub-reports.

If a different value in a matching column is indeed a correct value,
you may consider defining a VIEW with ALIAS names and then create a
sub-report based on that VIEW.

Take a look at the sub-reports and nested sub-reports included with
Running R:BASE Your Way! (Part 14) to understand the relationship.

To evaluate the exact relationship between all tables associated in
a Multi-Table Form, Sub-Report or Nested Sub-Report, you may also
take advantage of R:ColumnAnalyzer76 or R:ColumnAnalyzer80 Plugins.

Hope that gives you some blues clues ...

Very Best R:egards,

Razzak.

--- RBASE-L
================================================
TO POST A MESSAGE TO ALL MEMBERS:
Send a plain text email to [email protected]

(Don't use any of these words as your Subject:
INTRO, SUBSCRIBE, UNSUBSCRIBE, SEARCH,
REMOVE, SUSPEND, RESUME, DIGEST, RESEND, HELP)
================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [email protected]
In the message SUBJECT, put just one word: INTRO
================================================
TO UNSUBSCRIBE: Send a plain text email to [email protected]
In the message SUBJECT, put just one word: UNSUBSCRIBE
================================================
TO SEARCH ARCHIVES:
Send a plain text email to [email protected]
In the message SUBJECT, put just one word: SEARCH-n
(where n is the number of days). In the message body, place any text to search for.
================================================


Reply via email to