It may save a little space, but, if you check the size of the Session memo, it still can become a monster. If possible I wouldn't use either AVFPSessionTable or TrimMemo - just AVFPSession where TrimMemo wouldn't be necessary since it just uses memory in a very efficient way(this is the ASP Session object)...
>Hi Claude
>
>I have been going through the code and adding some more base methods to support my web framework and in the process making some minor tweaks. I came across trimMemo and could not really see the value so I just wondered if there was something I missed.
>
>Thanks
>Simon
>
>>It may not actually be doing any good. The idea was to keep the size of the memo down using any means possible. Is there a reason you're using AVFPSessionTable instead of AVFPSession? One of the things I'll be changing in the next version of AVFP is to use AVFPSession as the default instead of AVFPSessionTable since it's faster and requires less maintenance(packing the Memo file). It uses the exact same parameters so it would be easy to switch if you wanted to...
>>>Hi Claude
>>>
>>>I am not sure why you need the trimMemo method in the AVFPSessionTable class. Can you explain the reason?
>>>
>>>Thanks
>>>Simon White