Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.databases.paradox    |    To crash or not to crash, asks Borland    |    9,834 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 9,504 of 9,834    |
|    Jim Moseley to All    |
|    Formatted memo causes CPU to 100%    |
|    21 Nov 08 01:13:49    |
      From: jmose@mapson.attglobal.net              Greetings all.              I've now run into this issue twice in a year, so it's an epidemic! There       are several formatted memo fields on a table. Twice now, when a user is       trying to view or edit one of those fields, the system slows to a crawl &       the CPU jumps to 100% for a minute or longer. Eventually, it returns to       normal.              What I have determined is that somehow the formatted memo field's value is       corrupt, causing this behavior. To fix this, the entire value must be deleted       & then reentered. I even got a strange Pdox message today 'internal catalog       size exceeded', which got no hits on Google.              Does this sound 'normal'? Any ideas on the cause? Also, any good ideas       on how to programmatically check all records to see if any other rogue values       exist?              Thanks,       Jim Moseley              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca