On 3/23/02 3:04 PM, "Richard Perlman" <[EMAIL PROTECTED]> wrote:

> Paul's advice is, by my experience, accurate.  However, also based on my
> experience, once this starts, it just keeps on happening.  IMHO, this
> problem is the result of a bug that MS can't identify or doesn't want to
> fix.

Trust me, if it is something we can identify, we will fix it. When databases
go bad, they invariably end up in my lap. It is a real pain in the butt to
try and figure out what causes the problem. Many of the times it is the
result of a truncated database or messages file. We have tried and tried to
figure out what causes that to happen. None have been successful to this
point.


-- 
To unsubscribe:                     
<mailto:[EMAIL PROTECTED]>
archives:       
<http://www.mail-archive.com/entourage-talk%40lists.letterrip.com/>
old-archive:       
<http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>

Reply via email to