Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
What causes memo bloat?
Message
From
01/08/1999 23:26:40
 
 
To
31/07/1999 19:13:45
Dragan Nedeljkovich (Online)
Now officially retired
Zrenjanin, Serbia
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00248272
Message ID:
00248741
Views:
15
>>Hello David.
>>
>>Thanks for the quick description of memo defragmentation. I knew pointers were all that was stored in the DBF, but I never really thought about what was done with the FPT files when memos were edited. If it wasn't done this way, the FPT would have to have a pointer to the next fragment of the memo when memos were edited to larger than original. The way it is done, memos just need a start (pointer in the DBF) and an End of Memo character.
>>
>>Just a note: PACK w/o the MEMO or DBF clause will also PACK the memo file (according to the VFP 5.0 Help System).
>
>And another note: there's no such thing as EndOfMemo character - the memo block has a header which denotes its status and length. Fox never analyzes the content of the memo, and doesn't really care what sort of butes you stuff inside, else we'd never be able to Save To Memo, Append Memo From (file) etc, i.e. it wouldn't allow arbitrary binary content.

There is an end of memo word -- 0x1a1a. This is a hold over from dbase.

The following site has detailed descriptions:

http://www.e-bachmann.dk/docs/xbase.html
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform