Christian: I have reported this problem to MS in great detail. It is my opinion that there is a bug - MS has not ever responded on that assertion, they have only offered work-arounds. My simple reasoning is that a well built product should not become corrupted on a weekly basis (or more often).
Note that turning off Live-Sync seems to have reduced the problem. However, I liked the Live-Sync feature and I don't see why I should have to give up a feature just to avoid corrupted databases. That sure sounds like a bug to me. Yes, a "rebuild" temporarily resolves the problem. However, I have had three cases in which a "typical rebuild" did not work and I had to do an "advanced rebuild," resulting in a loss of data (links, flags, preferences, etc.). Data loss is NEVER acceptable. (Note. The data loss from an advanced rebuild is a documented consequence of the rebuild.) > Advanced rebuild Repairs damaged data and reduces the size of the database. > Because this option repairs data, which can result in data loss, you should > use it only after you've performed a typical rebuild of the database and > determined that problems continue to occur. > Also, it's important to note that after you perform an advanced rebuild you > will have to do the following: > � Re-create links between items, if you previously linked items to one other. > � Re-download messages from your IMAP, Hotmail, and news accounts. > � Reset column preferences in message folders for IMAP, Hotmail, and news > accounts. > � Reenter settings for schedules that send or receive messages from IMAP, > Hotmail, or news accounts. > � Reenter settings for rules that copy or move messages to folders on an IMAP > or Hotmail server. Since I use an IMAP server, there is no data loss for e-mail content. It is not clear what would happen for a POP server, for which mail was deleted after download. As the manager of a large, complex, software product, I would not accept it as "normal" if our product became "unusable" at frequent intervals. I expect a similar standard from MS. Richard On 3/23/02 3:10 PM, "Christian M. M. Brady" <[EMAIL PROTECTED]> wrote: > On 3/23/02 5:04 PM, "Richard Perlman" <[EMAIL PROTECTED]> wrote: > >> Etienne: >> >> 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. >> >> Richard > > Wow! That is a pretty big assertion and quite a leap in reasoning. Have you > been able to identify the bug? If so, please share it with us and keep the > conspiracy theories to a minimum. > > Cb > cbrady @ tulane.edu -- 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/>
