Rbase has available a nice PLUGIN RColumnAnalyzer76.rbl that can help in determining if you have duplicate column names
Jim Bentley American Celiac Society jan johansen wrote: > Jennifer, > > You may have noticed by now that any sub-table in the report > should only have ONE linking column. So if you are looking at > CUSTOMERS with the PK being CUSTID then you can easily > create sub-reports on CONTACTS, INVOICES, PAYMENTS, etc. > that only have the one linking column of CUSTID. > > If there is more than one common column the results may not > be displayed. You mention that you are using TEMP tables. > Look through all of them to make sure that you get uniqueness > i.e. if you have CompanyName in one table and if you have > CompanyName in a sub-table, rename CompanyName in the > sub-table to CompanyNameSub1. > > One way to check all the proper relationships is to start removing > columns from the sub-reports until something starts appearing. > Then you know where the problem lies. Or just start out simply > with one column in each subreport that you know have the proper > relationships and it should work for you. > > Also check to make sure you are working on the latest update 30315 I think. > > Jan > > > > -----Original Message----- > From: "Roberts, Jennifer" <[email protected]> > To: [email protected] (RBASE-L Mailing List) > Date: Wed, 1 Apr 2009 12:02:14 -0400 > Subject: [RBASE-L] - RE: Sub-Reports Question > > > I think that I must be missing something else. I have tried every which way > I can think of to get these reports to show. Only one of the sub-reports > will show. Nothing seems to be working and I am at a loss as where to go > next. I have looked at the pdf and the help and the examples, but > unfortunately I am still missing something. > > Thank you all for you help and suggestions. I’ll keep pecking away at it > and maybe I’ll stumble on what is wrong. J > > Thanks, > Jennifer > > From: [email protected] [mailto:[email protected]] On Behalf Of Gunnar > Ekblad > Sent: Wednesday, April 01, 2009 11:23 AM > To: RBASE-L Mailing List > Subject: [RBASE-L] - RE: Sub-Reports Question > > Jennifer Armin and others > I tend to agree with Dennis and Dan. For a temp table there is no need. > However if you really think there is a need dont create a temp table, create > a semi temp perment table, then you have all the possibiltes. > What I mean with a semi temp permanet table is a table that is perment from > R:Base point of view but temp from application point of view. > I use that sometimes when I need to make an ODBC query from Excel and that > works for me, then it have to perment ro able to read over ODBC but it is > realyy temp since I drop it as soon I am finished. > If you are in a multiuser enviroment then you maybee need to be clever to > name the semi temp permanet table like including the username in the > tablename > > > Gunnar Ekblad > > -----Ursprungligt meddelande----- > Från: [email protected] [mailto:[email protected]] För Roberts, Jennifer > Skickat: den 1 april 2009 15:02 > Till: RBASE-L Mailing List > Ämne: [RBASE-L] - RE: Sub-Reports Question > Hi Dan, > > I’ve tried to create a temp table and link one of the columns to my main > table. I am using the following code: > > ALTER TABLE `TSUBEA` ADD FOREIGN KEY + > (`CaseManager` ) REFERENCES `Security` > > I am receiving an error message that the referenced table doesn’t exist. > Do you have to do something special when trying to add a foreign key to a > temp table? > > Thank you, > Jennifer > > From: [email protected] [mailto:[email protected]] On Behalf Of Dan Goldberg > Sent: Tuesday, March 31, 2009 2:58 PM > To: RBASE-L Mailing List > Subject: [RBASE-L] - RE: Sub-Reports Question > > I just did a report with a dummy master table and six tables as sub-reports. > None of the columns had a relationship to each other. > > I had to have a linking table between the master table and the slave tables. > Since I was creating temp tables, I just used a bogus column in all the > tables and put a value in it to link them. Without the linking column it > does not work. > > When I created the temp table I made sure that no table had a linking column > to each other or the master except the bogus column. > > Dan Goldberg > > > > > From: [email protected] [mailto:[email protected]] On Behalf Of Roberts, > Jennifer > Sent: Tuesday, March 31, 2009 10:33 AM > To: RBASE-L Mailing List > Subject: [RBASE-L] - Sub-Reports Question > Hello, > > I would like to display a report with four slave tables and four > sub-reports. My slave tables are actually temporary views that are created > before the report generates. I am only able to get one sub-report to > display. I am using the child option, and I have them shifting relative to > the report in front of it. Currently all the reports are in the detail band > of my main report. I have tried moving them each to a band of their own and > then making them section reports and that didn’t work either. > > Is there some sort of settings – like with the forms – where you can set > your table settings, such as one to one or one to many? For a report, does > the slave tables have to have a column in common with the main table for > items to display? > > Thank you for any help. > > > Jennifer Roberts > Business Applications Specialist > Ohio Masonic Home > > This electronic message contains information from The Ohio Masonic Home, its > operating subsidiaries or affiliates. The information may be confidential, > privileged or otherwise protected from disclosure. The information is > intended to be received solely by [email protected], for use as designated > in the message. If you are not the designated recipient, you are instructed > not to review, disclose, copy, distribute or otherwise use of this > transmission or its contents. If you have received this transmission in > error, please notify The Ohio Masonic Home immediately at > [email protected]; in addition, please delete your record of > transmission. Sending, receiving, downloading, displaying, printing material > that is harassing, fraudulent, offensive, intimidating, defamatory, or > otherwise unlawful or inappropriate is strictly prohibited by The Ohio > Masonic Home. > > > This electronic message contains information from The Ohio Masonic Home, its > operating subsidiaries or affiliates. The information may be confidential, > privileged or otherwise protected from disclosure. The information is > intended to be received solely by [email protected], for use as designated > in the message. If you are not the designated recipient, you are instructed > not to review, disclose, copy, distribute or otherwise use of this > transmission or its contents. If you have received this transmission in > error, please notify The Ohio Masonic Home immediately at > [email protected]; in addition, please delete your record of > transmission. Sending, receiving, downloading, displaying, printing material > that is harassing, fraudulent, offensive, intimidating, defamatory, or > otherwise unlawful or inappropriate is strictly prohibited by The Ohio > Masonic Home. > > > --- RBASE-L =======================3D=======================3 D= 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) =======================3D=======================3 D= TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [email protected] In the message SUBJECT, put just one word: INTRO =======================3D=======================3 D= TO UNSUBSCRIBE: Send a plain text email to [email protected] In the message SUBJECT, put just one word: UNSUBSCRIBE =======================3D=======================3 D= 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. =======================3D=======================3 D=
