Welcome To The Home Of The Visual FoxPro Experts  
home. signup. forum. archives. search. google. articles. downloads. faq. members. weblogs. file info. rss.
 From: Dale Dedoroy
  Where is Dale Dedoroy?
 Bacolod City, Negros Occidental
 Philippines
 Dale Dedoroy
 To: Ryss Unger
  Where is Ryss Unger?
 Cape Town
 South Africa
 Ryss Unger
 Tags
Subject: RE: Another reason to use normal memo for archive
Thread ID: 229 Message ID: 252 # Views: 2 # Ratings: 0
Version: Unknown Category: General VFP Topics
Date: Sunday, May 20, 2001 10:53:10 PM         
   


Hi Guys,
If you remember in the old webboard, Ryss and I had expressed our own preferences regarding the subject.

Microsofties opted to add extra bytes (by blocks) in memos regardless of what you did on the resource file whether you add, reduce the size, reduce the resolution, whatever, instead of reflecting the real size of the file. My hunch is, they went for speed over efficiency of handling memos similar to MS-Word's "Allow Fast Save" option where any changes are added to the end of the file. I repeat, this is just my hunch. It would be nice if someone close to the guys in Redmond could confirm our guesses for us.

Additionally, VFP's tables are designed for shared environment. So technically you need to have the file used in exclusive mode before you can pack the file. It would be hard (again, my hunch) if the packing of memos be built-in into VFP internals. Assumming that it could be done, I'm very sure that there will be performance degradation which in turn, goes back to the speed issue. So by design, the people who wrote VFP leave the handling of memos to us, VFP users and programmers. My suggestion, therefore, to VFP architects if they can read this, is: Why not employ the auto-packing of memo files in USE (no parameter), CLOSE ALL and similar commands? When VFP processes these commands, it should attempt to re-use the table in exclusive mode if the table has a corresponding .FPT file. If somebody is still using the same file, then VFP will leave the memos alone. If it is successful in using the table in exclusive mode, pack the memos. If one is inquring the size of an FPT file, it shall display the huge (unpacked) size if somebody in the network is still using it. When the last user closes the file, the memo file then displays the correct and compact size. This way, only the last user shall suffer any performance degradation.

Hope I make sense.
Dale

ENTIRE THREAD

General fields and bloated FPT Posted by Philippe Sevin @ 5/18/2001 1:09:48 PM
RE: General fields and bloated FPT Posted by Eric den Doop @ 5/18/2001 1:40:13 PM
RE: General fields and bloated FPT Posted by Philippe Sevin @ 5/18/2001 2:07:46 PM
RE: General fields and bloated FPT Posted by Paul Culbertson @ 5/18/2001 2:22:39 PM
RE: General fields and bloated FPT Posted by Philippe Sevin @ 5/18/2001 3:15:35 PM
RE: General fields and bloated FPT Posted by Eric den Doop @ 5/18/2001 7:00:28 PM
RE: General fields and bloated FPT Posted by Philippe Sevin @ 5/18/2001 8:13:09 PM
RE: General fields and bloated FPT Posted by Eric den Doop @ 5/19/2001 6:53:33 PM
RE: Another reason to use normal memo for archive Posted by Ryss Unger @ 5/20/2001 11:57:27 AM
RE: Another reason to use normal memo for archive Posted by Ryss Unger @ 5/20/2001 5:35:37 PM
RE: Another reason to use normal memo for archive Posted by Dale Dedoroy @ 5/20/2001 10:53:10 PM
RE: The real story ... Posted by Eric den Doop @ 5/21/2001 9:39:20 AM
RE: The real story ...Network Traffic Posted by Ryss Unger @ 5/21/2001 12:30:52 PM
RE: General fields and bloated FPT Posted by Thomas Holt @ 5/21/2001 4:57:29 AM