On 1/28/02 2:22 PM, "Diane Ross" <[EMAIL PROTECTED]> wrote:

> On 1/28/02 5:40 AM, "Greg Cook" <[EMAIL PROTECTED]> wrote:
> 
>> Here's what I would do. First, backup everything. Second, try to rebuild the
>> database that has everything (opens fine) one more time. If it fails, I
>> would just open it, copy the messages from the 9-days that you have lost -
>> you should be able to just drag the messages or folders to a folder on your
>> computer, and it will export it as an mbox file (is that right?). Then, open
>> the good database that is most current (lost 9 days) and drag those mboxs
>> into that. It will import the messages into a new folder probably. Just move
>> those messages to whatever folders you had them in originally.
> 
> That would be my suggestion too. I also use the mbox method to archive mail
> into anther identity.

Greg and Diane,

Thanks for your continued help.

Exploring a bit more, I find that the most recent copy of my database on my
desktop Mac, dated 1/17, is ALSO corrupt and cannot be rebuilt using the
typical rebuild. What happens when I attempt to rebuild the database on the
desktop Sawtooth AGP-G4 is exactly what happens on my Ti PowerBook, namely
the progress bar doesn't make it to the last message before jumping from the
compacting step to the optimization step, and then nearing the end of
optimization a dialog appears saying the database probably cannot be
rebuilt. (I have not done an advanced rebuild on the AGP-G4 database to see
if it discards everything since 12/9; I assume it would).

So, I'm guessing that the database corruption didn't happen because I
force-quit Entourage on January 26th, but rather that something happened
(probably December 9) that didn't become evident at the time, and which only
causes problems when I try to rebuild the database.

Therefore, it appears that to get a GOOD database I'll have to export all
messages from December 9 onward from the CORRUPT database to desktop mbox
files (one folder at a time) and reimport them into the rebuilt database.

My concern now is that perhaps one of the messages from December 9 or 10 is
ITSELF what makes the entire database corrupt, and that the act of
exporting/importing messages from the corrupt database to the rebuilt but
truncated one will corrupt the new database.

Would you suggest I do a typical rebuild after importing each folder's worth
of messages into the new database?

Since the program functioned apparently normally from 12/9 to 1/26 without
any obvious problems, would you suggest that users do a routine rebuild
frequently so that if something like this happens again, the damage would
affect only one or two days worth of work? My concern here is that, even
assuming I can retrieve all my messages, I've obviously lost their links to
each other, which is one of the reasons I'm USING Entourage instead of
Apple's "Mail" program (the other, of course is because I anticipate being
able to maintain a single calendar and address database on Macs and Palm
once MS releases a conduit).

Entourage is a great program, and I'm delighted with its performance despite
being smacked by this database corruption. I'm trying to fit the way I work
to its foibles.



Jim Robertson
-- 



-- 
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