74461e94   
   From: info@sundialservices.com   
      
   kryten wrote:   
   > I have a legacy tool that uses Paradox database files.  There are some   
   > tables that are too large and I used Access to delete records from   
   > them.  However, the file sizes for the Paradox tables did not decrease   
   > like I expected them to.  Is there a tool that I could use that would   
   > compact the tables to reflect the new amount of data?   
   >   
   > I know that Access has to be compacted on occasion because the objects   
   > in the database keep their memory size even though data or code has   
   > been deleted.   
      
   Paradox "recycles" the space in a database file.  Records are stored   
   in "blocks," and when all of the records in a block are deleted the block   
   is placed onto a free-list for reuse.   
      
   It's actually very inefficient to grow or to shrink a file in most   
   filesystems, so Paradox doesn't shrink a file at all and it grows a file   
   only when the free-space list is exhausted.  This is by design.   
      
   Furthermore.... you'll see that Access does the same thing.  Pretty much   
   every database management system does it.   
      
      
   ----   
   ChimneySweep(R): Fast(!) table repair at a click of the mouse!   
   http://www.sundialservices.com   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)