Jim,
A useful recommendation could be to create all the needed temp tables in one
go in a stored procedure.
The only thing you'll need to do, after having opened the database, is to
run this procedure.
You are able to create empty tables and fill them when needed.
The nice thing about temp tables is that they are unique per user, this
could influence the performance positively.
To give you an idea how it looks like, an example:
DROP PJT_PROJECT_SEARCH
PROJECT TEMP PJT_PROJECT_SEARCH +
FROM PJT_PROJECT USING PJT_ID, PJT_ID_REFER_TO,........ +
WHERE LIMIT = 0
CREATE INDEX PJT_REFER_SEARCH ON PJT_PROJECT_SEARCH (`PJT_ID_Refer_to` ASC
SIZE 14 )
CREATE INDEX PJT_ID_SEARCH ON PJT_PROJECT_SEARCH (`PJT_ID` ASC SIZE 14
)
1 drop temp table
2 create new temp table with no rows (limit = 0)
3 create indexes
The benefit of doing it this way is that you keep a clear view upon the
status of all used temp tables in your application
Hope this helps
Tony IJntema
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Jim Belisle
Sent: zondag 18 juli 2010 15:17
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: mdi forms
Razzak,
Now that I know MDI forms can use temporary tables, I can do my
detective work. I will have to check my code.
On the particular form I am talking about, I create two temp tables, one
of which is in a scrolling region. I will have to find out why the
scrolling region table is not being created. That is the error I get -
no table found.
I just want to take this time again to thank you Razzak for having a
forum like this where people can get information "on the fly" so to
speak. For someone like myself, that does programming on the side, it
has been invaluable. Also all the forms, tables etc we receive when we
purchase the product have made me look smart when I meet the needs of
our users.
I hope as RBASE grows with continued success these "extras" are not ever
dropped.
Jim
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of A.
Razzak Memon
Sent: Saturday, July 17, 2010 10:21 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: mdi forms
At 06:34 PM 7/17/2010, Jim Belisle wrote:
>I have been successful in getting forms to come up as MDI
>when they are based on tables. I have so far been unable
>get other forms to come up as MDI that use temp tables. Is
>this always true? Is there some special programming that I
>must do for temp tables to be used as MDI?
>
>Jim
>
>Sorry! I meant to say FORMS BASED on temp tables to be used
>as MDI.
Jim,
Any form used as MDI, either a Variable Form, or a form based
on a permanent/temporary table, should always work as expected.
In your specific case, just make sure that the actual temporary
table is defined prior to using the form as MDI.
Where in your routine are you defining TEMPORARY table(s) for
all those MDI forms based on TEMPORARY tables?
Did you know that you can define the appropriate temporary
table(s) related to any specific form as "On Before Design"
and "On Before Start" EEP?
Also, keep in mind that all TEMPORARY Tables/Views are DROPped
when using the DISCONNECT command.
Last but not least, you may TRACE your routine to pin down
the actual problem.
Very Best R:egards,
Razzak.
