From: info@sundialservices.com   
      
   dmacias666@LABridge.com wrote:   
      
   > My supervisor uses Paradox 10 for all his reporting for well over a   
   > decade.   
   > Just recently, he has encountered a "table full" error.  He is working   
   > with a very large set of data; over 416,000 records with 300 columns per   
   > record. His systems is running XP Professional with a P4 running at 3 GHZ   
   > with 2   
   > Gigs of memory.   While searching the web I found a reference to a fix   
   > that involving changing the block size.   
   >   
   > Can anyone suggest a fix or point me in the right direction t fix his   
   > problem.   
   >   
   > David Macias   
   > Research Technician   
   > CSUDH   
   > Institutional Research   
   > dmacias@csudh.edu   
      
   Here's the basics...   
      
   A Paradox table consists of up to 65,535 "blocks" of information, each   
   containing an integral number of records.  (There are 6 bytes overhead per   
   block.  Records do not wrap-around.)   
      
   From this, knowing the block-size, you can calculate the maximum theoretical   
   capacity of an _unkeyed_ table.  But here's a catch:  the index files have   
   the same architecture, and they contain not only abbreviated records ("just   
   the keys, ma'am...") but also a B-tree index structure.  When any index is   
   full, so is the table.   
      
   If you have a very, very large amount of data and are starting to run into   
   table-capacity issues, you should look carefully at the overall strategy of   
   the application:  can the information be subdivided into smaller tables?   
      
   ----   
   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)