What exact version and build of R:BASE are you and your clients using
with that exact symptom?
I bet you are not using the latest updates of R:BASE or R:BASE Compiler.
FWIW, there have been a few enhancements related to Turbo V-8 in the
last uodates, and a MAJOR enhancement is scheduled for the upcoming
update specific to Turbo V-8 handling 64-bit pointers for PK/FK and
INDEXes.
Of course, currently under private beta, these updates will be
available to all R:SAP subscribers and those who have purchased the
product within one year.
Very Best R:egards,
Razzak.
Sent from my iPhone
On Jun 24, 2009, at 1:21 PM, Lawrence Lustig <[email protected]>
wrote:
Hi all.
I have an application in which I'm getting occasional weirdness in
the indexes for one particular table, leading to incorrect results
on some queries.
I've been able to fix this with other users on-line by using the
PACK INDEX <IndexName>. It's a big help to be able to do this with
users in the system.
Unfortunately, that only helps me AFTER the users have experienced
and noticed the problem. I'm thinking of implementing an automatic
PACK INDEX routine to run at night to catch these things in
advance. This database runs 24 hours, but it's less busy at night.
My only concern is that by rebuiling these indexes repeatedly, my #3
file will grow in size.
Does anyone have experience with this? Is that what happens? Or
does R:Base somehow recycle the space currently used by an index?
--
Larry
