Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uflorida!mephisto!prism!jgb
From: jgb@prism.gatech.EDU (James G. Baker)
Newsgroups: comp.databases
Subject: Re: Clipper and lost memo records ... HELP!
Message-ID: <12270@hydra.gatech.EDU>
Date: 7 Aug 90 01:43:51 GMT
References: <13220.26b95be0@qut.edu.au>
Organization: Georgia Institute of Technology
Lines: 31

In article <13220.26b95be0@qut.edu.au> zlcbeowen@qut.edu.au writes:
>After some months of operation, a .DBT file has grown to 16M, and now
>we are having problems ...
> 
>Now when calling up the memo field of any record in the file using MEMOEDIT(),
>the memo field is deleted on returning... [by this line of code:]          
> 
>    REPLACE biblio WITH MEMOEDIT(biblio,tr+1,tc+2,br-1,bc-2,.t.,"memo_func",;
>        "","",init_row,init_col,init_rel_row,init_rel_col)

I have had similar problems with memo fields.  Although "packing" should help,
a true "COPY TO" seems to be the most help.  Also, is your "memo_func" doing
anything tricky like opening other files or messing with SET KEY's?  If you
have the memory, load the record to a memory variable and see what step 
zaps the string.

     Mbiblio = BIBLIO
     altd()                                   && Call up debugger of choice
     Mbiblio = MemoEdit( Mbiblio, .... )
     altd()           
     REPLACE BIBLIO WITH Mbiblio
     altd()

See if it sheds any light on the problem...


-- 
BAKER,JAMES G - Lab Technician, School of Electrical Engineering
Georgia Institute of Technology, Atlanta Georgia, 30332
uucp:	  ...!{decvax,hplabs,ncar,purdue,rutgers}!gatech!prism!jgb 
Internet: jgb@prism.gatech.edu