"Doesn't want to fix"? Why would they not want to fix it? If you have a copy of a corrupt database smaller than 2GB which you can't fix, I'm sure they'd want to have a copy of it, if you don't mind, for them to track down whatever bug is preventing successful rebuild.
OTOH, if you're saying that you rebuild successfully, then it gets corrupted again and again, chances are greater that there is something else on your computer which you use with Entourage which is sending it corrupt data. Maybe messages from a particular sender, or maybe text or graphics from some other app which you paste in or attach. If you ever discovered a replicable pattern that caused corruption, they would very much want to know about it, whatever it is (whether a flaw in Office or in some other app). -- Paul Berkowitz > From: Richard Perlman <[EMAIL PROTECTED]> > Reply-To: "Entourage:mac Talk" <[EMAIL PROTECTED]> > Date: Sat, 23 Mar 2002 15:04:23 -0800 > To: "Entourage:mac Talk" <[EMAIL PROTECTED]> > Subject: Re: Iminent DB meltdown? > > 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 > > On 3/23/02 1:22 PM, "Paul Berkowitz" <[EMAIL PROTECTED]> wrote: > >> On 3/23/02 1:12 PM, "Etienne Michaud" <[EMAIL PROTECTED]> wrote: >> >>> Well after using Entourage v.X for a couple months, I'm having my first >>> scare. >>> >>> I had a mystery messge in my inbox according to the Folder list. >>> It appears as unread: Inbox (1), but I can't see the actual message anymore. >>> If I ask Erage to display only unread messages, I get an empty list. If I >>> scroll, I get a ribbed grey and white background, not the empty list white >>> background >>> If I then click in the list, I get an Error 4236 message and a subsequent >>> crash (see crash log included below). >>> >>> Suggestions? I backed up my database, but the backed up copy has that >>> mystery message in it. Is a rebuild safe in that situation >> >> That's precisely what rebuilds are for, Etienne. After you rebuild, and all >> goes well, back up the rebuilt database and throw away the old backup as >> well as the old database. (Or in a worst-case scenario, you have your old >> backup to copy, open and do more rebuilding with.) > > > -- > 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/> > -- 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/>
