Welcome To The Home Of The Visual FoxPro Experts  
home. signup. forum. archives. search. google. articles. downloads. faq. members. weblogs. file info. rss.
 From: Ilya Rabyy
  Where is Ilya Rabyy?
 Fountain Valley
 California - United States
 Ilya Rabyy
 Tags
Subject: FoxPro Advisor: preventing FPT bloating
Thread ID: 78594 Message ID: 78594 # Views: 2 # Ratings: 0
Version: Not Applicable Category: Databases, Tables and SQL Server
Date: Wednesday, October 05, 2005 10:31:56 PM         
   


Colleagues:

Here's the address to the very interesting article in the FoxPro Advisor magazine on the net:

http://advisorupdate.info/Articles.nsf/nl/17164.

In this article, Tamar Granor speaks of the ways to avoid "bloating FPT" files. Summarizing, it appears that the most convenient way to prevent overbloating FPT file is to set BLOCKSIZE to 0. However, this works only for the newly created tables with Memo field, existing tables remain having the block size the same as it has been set at the moment of creation of these tables.

Hence the questions:

1. Is the block size saved in the DBF - or what? - file header?

2. Is it possible to do BLOCKSIZE = 0 in Config.FPW?

3. If I append - or INSERT FROM MEMVAR - records into a table created with non-zero block size (say, default 64) in a session where BLOCKSIZE = 0 is set - to which setting the VFP data engine would comply while updating the FPT file: original or the current?

TIA!

Regards,

Ilya

ENTIRE THREAD

FoxPro Advisor: preventing FPT bloating Posted by Ilya Rabyy @ 10/5/2005 10:31:56 PM