On 11/7/02 6:59 pm, "Julian Vrieslander" wrote: > But I am still wondering about that MS Database Daemon - and whether it is > necessary to shut it down before doing a backup. From earlier messages in > this thread, and from messages sent to MacFixit, it appears that the Daemon > keeps the DB file open and that this might be causing problems for some > people. It's not hard to see why it is necessary to kill the Daemon when > doing a restore/replacement of the DB. It's less clear why the Daemon, or > an open DB file, would be causing problems when the DB file is copied to a > backup.
I have been corresponding off-list with a Entourage user who was having to rebuild his database every time he copied the identity from his desktop to his iBook (or vice-versa). While he was not using Retrospect, he was using a utility that seems to just do a finder copy to move the data across. He had not been quitting the daemon before copying, but when I advised him of the script to quit the database first� this solved all the problems. So, it appears that copying the database with the daemon running CAN muck things up, but doesn't always do so. � the script: Tell app "microsoft database daemon" to quit -- Barry Wainwright <http://www.barryw.net/> "You can't hide a piece of broccoli in a glass of milk." -- Amir, age 9 -- 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/>
