Julian Vrieslander <[email protected]> wrote on 10/15/09 6:38 PM:
> I don't understand why you are thinking of moving your existing Address Book > and iCal apps from 10.4.11 to 10.6.x. Snow Leopard has newer versions of > those apps - replacing them with older versions will probably cause huge > problems. Perhaps what you mean is that you want to migrate the data files > from your old installations. This might be possible by using the import > capabilities of the newer app versions. But if you will be syncing with > Entourage, why not let Entourage set all the data in Address Book and iCal, > when the first sync is done? I meant to say that I want to migrate the data from iCal and Address Book.app in OS 10.4.11 into the new iCal and Address Book.app in the new OS 10.6.x. I also want to migrate both the existing Entourage 2004 database into the new Entourage 2004 installation. I prefer to use both iCal and Address Book.app data and also Entourage's calendar and address book because the two (Entourage's database and Apple's database) don't hold exactly the same data. For example, Entourage's calendar has a field for "travel time," which iCal does not. iCal's events have a field for multiple alarms, and Entourage's calendar does not. I'm afraid that if I migrate the data from old iCal into new iCal, and also migrate the data from old Entourage and new Entourage, and then sync new Entourage with new iCal, all the events will get screwed up. I have had many sad occurrences where Entourage or iCal has overwritten the data of the other -- resulting in something like "654 events were changed." And since I sync Entourage <-> iCal on MacBook Pro, and also sync Entourage <-> iCal on iMac, and also sync iCal on MacBook Pro <-> iPhone, and also sync iCal MacBook Pro <-> iCal iMac (using SyncTogether)... ...I am trying to figure out in advance how to minimize the opportunity for multiple erroneous calendar changes with each database trying to overwrite/change the other database. I avoid this now by making a backup of iCal's databases before I do any sync. If there's a screw-up, I can restore from the most recent database. [By the way, we know that MobileMe is supposed to be able to handle the multiple device syncing, but I'm not confident that MobileMe syncing is reliable.] > I did not notice any huge improvements or enhancements in Entourage when I > migrated from Office 2004 to 2008. There are a few cosmetic changes, and a > new companion organizer app (My Day) which I do not use. The main reason I > upgraded was to get some specific improvements in Excel. I often need to > save tab-delimited text files out of Excel, and doing this in the 2004 > edition is needlessly complicated. Two things to watch out for if you move > to Office 2008. The UI in Word is significantly changed - you may or may > not like the changes. And MS dropped VBA (Visual Basic for Applications) > from Office 2008. If your workflow uses VBA macros, you will probably want > to stick with 2004. The next major version of Office will restore VBA, and > MS recently announced that they will support Office 2004 until 2012. Thanks for that. Best/Roger+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Roger S. Cohen, President, Cohen International [email protected] http://www.rogercohen.com Voice: +1 (845) 358-8936 Fax: +1 (845) 358-8937 -- YouTalk mailing list List address: [email protected] List information: http://entourage.mvps.org/support_options/list.html List moderator: [email protected], [email protected] To unsubscribe: mailto:[email protected]?subject=unsubscribe
