Yeah so I'm out of my league then. Never have used sub reports and really I'm not sure what they are used for. I've only done lots of 5 table reports with break headers and footers. I also like to "clone" forms and reports to use the same formatting and style over and over for different tables.
On Fri, Oct 7, 2011 at 8:59 AM, jan johansen <[email protected]>wrote: > Bill, > > But in this case you wouldn't use a view. > The beauty of subreports is that you treat it like a Slave/Master form. > Each subreport has a single linking column to the master table. > Avoid putting any of the subreports in a detail row. > > Jan > > > > > -----Original Message----- > From: William Stacy <[email protected]> > To: [email protected] (RBASE-L Mailing List) > Date: Fri, 7 Oct 2011 08:53:37 -0700 > Subject: [RBASE-L] - Re: a report with one master table and 4 slave tables > > The only other thing I can think of is that the view is damaged. By that I > mean I presume the report is based on a view that contains all 5 tables? > Sometimes a column here or there gets unchecked for inclusion in the view, > or maybe there's some error in the view links. Finally, the report itself > might have gotten damaged. I've certainly had that happen where I had to > reconstruct the report from scratch. You might try a very simple report, > test it, then go more and more complex with each iteration. > > On Fri, Oct 7, 2011 at 8:23 AM, A.G. IJntema <[email protected] > wrote: > >> Yes, there is only one common column name. I agree never use the same >> column name in tables. >> The fact is that the report works fine as long as I use only one slave >> table, so I cannot find logic behind this problem. >> >> BTW >> >> My solution for avoiding double column names is to start every table name >> with an abbreviation of 3 or 4 characters followed by an underscore and then >> a logical name. >> The same applies to the column names. They all start with the same >> abbreviation followed by an underscore and then a logical name. >> Only foreign keys do have the same name as in the original master table. >> >> For instance: >> >> Table: CCT_Client >> Possible Column names are: >> >> CCT_ID which is always the PK >> CCT_Name Name of the client >> CCT_Zipcode Zipcode >> And so on. >> >> It works fine, you don’t have to worry about using double column names and >> you’ll see in a glance to which table a column belongs. >> >> Using 9.1 64 you also don’t have to worry about the length of a column >> name. >> >> Tony >> >> >> >> * From:* [email protected] [mailto: [email protected]] *On Behalf Of >> *William >> Stacy >> *Sent:* vrijdag 7 oktober 2011 15:35 >> *To:* RBASE-L Mailing List >> *Subject:* [RBASE-L] - Re: a report with one master table and 4 slave >> tables >> >> A long shot: are you sure each child table has one AND ONLY ONE column >> (the foreign key) in common with it's parent table? Once in a while I'll >> have more than one inadvertently and that always messes things up. >> On Fri, Oct 7, 2011 at 6:27 AM, A.G. IJntema <[email protected] > >> wrote: >> Jan, >> >> Thank you, one moment I thought that does the trick, but from one slave >> table all rows are being printed and from the second only a few rows. I >> cannot think why this happens. >> >> Tony >> >> * From:* [email protected] [mailto: [email protected]] *On Behalf Of *jan >> johansen >> *Sent:* donderdag 6 oktober 2011 21:40 >> *To:* RBASE-L Mailing List >> *Subject:* [RBASE-L] - Re: a report with one master table and 4 slave >> tables >> >> Tony, >> >> Make sure that your sub-reports are not included in detail lines. >> >> Jan >> >> >> >> >> -----Original Message----- >> From: "A.G. IJntema" <[email protected]> >> To: [email protected] (RBASE-L Mailing List) >> Date: Thu, 6 Oct 2011 21:29:21 +0200 >> Subject: [RBASE-L] - a report with one master table and 4 slave tables >> I have one master table (client) and 4 slave tables (with all kind of >> test results). >> >> I like to create a report, starting with the master table and then the >> results of these 4 slave tables, which could have 0 to n rows each. >> >> I have found out that the first slave table is no problem, but then I am >> confronted with the fact that only 1 row from the second, third and fourth >> table is being printed. >> >> I have tried all kinds of variations, like putting them all in the >> detail section of the master table, or creating more levels in the report >> and put every slave table in a separate footer section. >> >> But I am not able solve this problem. >> >> Am I doing something wrong or is it impossible what I like to create. >> >> Hope someone can help me. >> >> Tony IJntema >> >> >> >> >> >> -- >> William Stacy, O.D. >> >> Please visit my website by clicking on : >> >> http://www.folsomeye.net >> >> >> > > > -- > William Stacy, O.D. > > Please visit my website by clicking on : > > http://www.folsomeye.net > > > > -- William Stacy, O.D. Please visit my website by clicking on : http://www.folsomeye.net
