Bill,

I beleive that the #4 file is also a double linked list.  I have not gone in 
and looked at one, but when I get time I will.  I have been scanning docs 
and storing them in the #4 file for almost 2 years.  I have over 80,000 
pages scanned being stored in a dozen databases.  I have never had a problem 
w/ the #4 file.  I must also say that I am not modifying data in the #4 
file.  I only do inserts and deletes.  I normally don't have more than a 
couple of people adding rows at one time.

Troy Sosamon

===== Original Message from [EMAIL PROTECTED] at 7/12/02 6:09 am
>I have an application that has outgrown the NOTE fields it is currently
>using to store TEXT.  I am contemplating using a VARCHAR to store the text,
>but I am relunctant to do the conversion without some indication from this
>list as to the robustness(sic) of R:BASE's file 4 structure.  I am very
>comfortable with the double link list structure of R:BASE's file 2 and
>would like to have the same comfort level with file 4.  However, I have not
>seen a good explanation of file 4's structure.
>
>I would appreciate any comments and especially comments relating to the
>following:
>
>  1.  Experience of corruption and ability to recover from corruption.
>
>  2.  Experience of heavy use. ie Many updates to existing records and
>corresponding changes in record lengths.
>
>  3.  Growth of the physical size of file 4 resulting from heavy activity.
>
>
>TIA
>
>Bill Perry - St. Louis
>
>================================================
>TO SEE MESSAGE POSTING GUIDELINES:
>Send a plain text email to [EMAIL PROTECTED]
>In the message body, put just two words: INTRO rbase-l
>================================================
>TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
>In the message body, put just two words: UNSUBSCRIBE rbase-l
>================================================
>TO SEARCH ARCHIVES:
>http://www.mail-archive.com/rbase-l%40sonetmail.com/

================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: INTRO rbase-l
================================================
TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: UNSUBSCRIBE rbase-l
================================================
TO SEARCH ARCHIVES:
http://www.mail-archive.com/rbase-l%40sonetmail.com/

Reply via email to