From: jmose@mapson.attglobal.net   
      
   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)