From: liz@paradoxcommunity.com   
      
   If the formatting is important, you may be in trouble...   
      
   I've never been able to fix a memo field without exporting the table to text   
   and re-importing.  This means removing all hard returns from memo fields   
   and losing any formatting in formatted memo fields.  Of course, I've only   
   ever had this happen once.  ChimneySweep wouldn't fix it; table repair wouldn't   
   fix it; making a new table and moving data (with query, table add, script)   
   wouldn't fix it.  Only making a new table and importing the data from a text   
   file would fix it.   
      
   That said, I never saw the error message you report, so maybe it's something   
   other than corruption (or a different kind of corruption).   
      
   Maybe others have alternatives.   
      
   Liz   
      
      
   "Jim Moseley"  wrote:   
   >   
   >Greetings all,   
   >   
   >A client is receiving a strange error with a Formatted Memo field "Error   
   >writing file - record not tagged".  This also causes a long delay in my   
   app   
   >trying to get the value - sometimes over 5 minutes, which causes the client   
   >to think it is locked & they restart the app (very bad!).   
   >   
   >The workaround is to wipe out this problem value, which fixes the problem   
   >for the one record.   
   >   
   >I'm writing a generalized script to fix every value.  The script copies   
   every   
   >value to a memo variable then to a backup table, & sets the production value   
   >to blank.  The table will then be closed, giving an 'empty' MB file.  A   
   second   
   >pass on the table then reverses this to restore all the values.   
   >   
   >My question is, will the 'corrupted' value survive being copied to/from   
   the   
   >backup, or will it 'fix' itself (and/or become blank)?  I'm hoping for the   
   >'fix' option.  The MB files are a mystery to me, so I don't know if the   
   corruption   
   >is in -how- the value is stored or is inherent in the value itself.   
   >   
   >Looking at Bertil's buglist, this only shows an Sql problem, which we don't   
   >use.  Also, there isn't an opportunity to redesign this without formatted   
   >memos, so I'd rather not have that discussion here.   
   >   
   >TIA,   
   >Jim Moseley   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)