Larry,
PACK INDEX or PACK INDEX FOR will both cause file 3 to grow. You need to periodically UNLOAD/INPUT to clean that up. Emmitt ----- Original Message ----- From: "Lawrence Lustig" <[email protected]> To: "RBASE-L Mailing List" <[email protected]> Sent: Wednesday, June 24, 2009 1:21:51 PM GMT -05:00 US/Canada Eastern Subject: [RBASE-L] - Pack Index and RB3 file size. 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
