Thanks
I figured it out
Marc
----- Original Message -----
From: Walker, Buddy
To: RBASE-L Mailing List
Sent: Sunday, November 23, 2008 8:58 AM
Subject: [RBASE-L] - RE: Which method is best?
Marc
You can create an index on temp tables so I would stick with the temp
tables. Also make sure scratch is set to a local folder.
Buddy
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of MDRD
Sent: Sunday, November 23, 2008 9:45 AM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Which method is best?
Hi
I use to use a permanent table then switched to a Temp table thinking it was
a better way to go.
Since I can not have indexes with a Temp table I an thinking the permanent
table might be faster,
especially on a slow network. (Staticdb On)
If I use the Temp table I create it each time the App is started, most
offices Exit Rbase at lunch and
restart it when they get back. A few offices said the form that uses this
table gets slower as the day
goes on. My thinking it is because of the lack of indexes?
When we start the form I
Delete All Rows in the Table
Insert Rows from the Hist table for the last invoice for that custnum
Edit Using the form Where Custnum = .vcust..make changes if needed.....there
is 3-4 rows in the form
Click a button that Inserts the Rows into the Hist table
Exit the form
Without indexes would the Temp table get bogged down with all the deleted
rows that linger around
until a Pack or drop and recreate the Temp table? I tried creating the Temp
table each time but that
slowed things down.
I thought the Temp table would be better with multiple users and there would
be less chance of users
deleting the other users rows since the Temp table is local on each computer.
If I use a permanent table I can Pack the Table each time they start the App,
which is morning and noon
for most offices.
Thanks for any advice
Marc
