Karen -
You have the FULL R:BASE Variable definition screen just like in a report -
you can create as many variables as you want and string them together and so
on.
When it says it can refer to only one report or view, it's the same as an
R:BASE report - it has only one driving report or view, but you can still
create report variables to get info from other tables or views.
Also - one new function that allows you to get lots of many-to-many values
on one report is the (LISTOF()) function. It may work for you, too, if you
set up your views properly in R:BASE.
R:Merge may not be your solution - but I'd try it before I went with the "A"
word... <g>
Sami
----- Original Message -----
From: "tellef" <[EMAIL PROTECTED]>
To: "RBASE-L Mailing List" <[EMAIL PROTECTED]>
Sent: Thursday, February 13, 2003 4:30 PM
Subject: [RBASE-L] - Re: My Complicated report example
Sami:
>R:Merge has a built-in R:BASE variable definition. As far as I have been
>able to determine, if you can create an R:BASE variable for it, you can
>create an R:Merge variable for it... That includes standard R:BASE lookup
>variables to other tables.
I don't think I can create *A* variable to do this. R:Merge documentation
says that it can refer to only one table or view. I cannot think of a view
I can create to base this report on. Data from the following tables need
to be on the report:
Table1 a single row table with linking field TableID
Table2 a multiple row table with the linking field.
Table3 another multiple row table, printing a table of data where
Codecolumn = 'A'
Table3 the same table, but later on it will print a table of data
where Codecolumn = 'B'
This is a SIMPLIFICATION of the report design. There's no way I can create
expressions to print multiple rows of data. I hate to use the "A" word,
but
Access has subreports and I'm thinking of using that with an ODBC link to
the
tables.
Karen
