Karen Whatever you do don't go for 'A'. That is bad language, bad practise and even worse it makes you sick the day after. Gunnar
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of tellef Sent: den 13 februari 2003 23:31 To: RBASE-L Mailing List 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
