Stupid @rn question

[Jean-Pierre A. Radley]

John Esak propounded (on Sat, Sep 23, 2006 at 07:32:06PM -0400):
| 
| > On Fri, Sep 22, 2006 at 08:04:44PM -0400, Scott Walker wrote:
| > @rn is is an eight character field.
| >
| > What's happens when an fp file goes about 99999999 records.
| 
| Well, let's see. Assuming you consider 1 megabyte to be 1000 kilobytes and 1
| gigabyte to be 1000 megabytes... (not 1024 kilobytes and 1024 megabytes...
| which, who knows may be what many consider them to be...)  In any case,
| Using the former suggestion...
| 
| npi-p7# bc
| 1024*1000
| 1024000         1 megabyte
| .*1000
| 1024000000      1 gigabyte
| .*2
| 2048000000      2 gigabyte file size limit on system filePro previously
| desgined on
| 
| And considering there is a 20 byte header for every record  in a filePro
| database (plus a zero'th record which will ignore for the moment.) And, you
| must have at least 1 byte in every record wouldn't you think, just to make
| it a record of *something*. ;-)  That would be:
| 
| 99999999*21
| 2099999979
| 
| So, you would hit the file size limit *before* you hit filePro's limit. No
| foul, no error. :-)
| 
| However, I know we've had this discussion here a few times before and I
| believe that the upshot is/was that filePro has made some allowance for @rn
| on platforms that can store files bigger than 2Gb. Which, means you can have
| somewhere around a bazillion records I think.

The specs on the fP web page still claim that the limit is 1 billion
records.  Does filePro generate extended key files if it hits an OS's
filesize limit?

-- 
JP
	==> http://www.frappr.com/cusm <==