Of course, with STATICDB ON that would not be an option. Dennis
________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Gunnar Ekblad Sent: Wednesday, April 01, 2009 10: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.
