From: jmose@mapson.attglobal.net   
      
   Tony,   
      
   >You talk about 'problem value' but don't identify what the   
   >value is - that might be helpful to know.   
      
   That's just it - once the field's value is corrupted, Pdox won't tell me   
   what it was.  I can only tell it was corrupted by the long delay in getting   
   the value, and the error message.   
      
      
   >Is the table damaged once the value has been assigned to the field?   
      
   Table Repair shows the table is fine, no corruption.   
      
      
   >Is this only happening on that one system?   
      
   It has now happened at 3 different clients over the last year (that I know   
   of, out of ~1000 total).  I can't reproduce it because I'm not sure what   
   is causing it in the first place.   
      
   So, my current goal is to just try to fix all values & see if that helps.   
    The latest client with the problem has started 'locking up' a couple of   
   times a day, so after my fix it should be quickly apparent if it had any   
   effect.   
      
   Thanks,   
   Jim Moseley   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)