The Office Palm conduit only supports one address per contact, whereas the
Tungsten T3 supports two. That may be the cause of your problems. We are all
hoping for an updated Palm conduit from MS which will handle this.
Have I understood your problem correct, or are you losing contacts
completely?
-Bo
There is another problem with contacts - a known bug going back at least two
versions. This bug bites when the 'default address' is set to 'Home' and
data is entered into the handheld device:
1. Enter the contact details including an address into the HandHeld device.
2. Sync the device to Entourage: the address gets posted to the 'home
address' field in Entourage in accordance with the conduit address
preference. However, Entourage's 'Default Postal Address' flag remains set
at it's default setting of 'Work'.
3. Sync a second time: Entourage syncs the contact's blank work address
back to the handheld, because it still has it's 'Default Postal Address' set
to 'work'. This effectively erases the address in the handheld, but it is
still in Entourage's 'Home Address' fields.
4. Sync a third time: Now, the Handheld contact has changed during the last
sync, so the contact is synced again. This time the now blank address is
synced back to Entourage's 'Home Address' field, effectively erasing the
data that was in there.
You have now lost the address in both Entourage and The Handheld.
There are two possible work-rounds:
A) Leave the Conduit set to default postal address being 'Work' -
everything will be preserved, but you will have to manually swap the
addresses in entourage to 'Home' after syncing - no need to worry now, the
correct flag will be set in entourage when you do this, so there will be no
more data loss (see below for scripts to ease this swapping)
B) Set the Default address to 'Home;' in the conduit, as you have it now,
but after each sync run one of the scripts posted below. These can detect
any mis-synced contacts and open them for you to manually correct the
'Default Postal Address' or swap the addresses over, or can automatically
reset the flag without many other intervention from you.
Now you know all this, PLEASE take the time to let Microsoft know that you
want this bug squashed - it's been this way ever since the first conduit was
shipped. You can send feedback directly to the development team through the
'Send Feedback' link in the Help menu.
The Scripts:
-- This script will open every contact which has a home address, but no work
address if the flag is mis-set.
tell application "Microsoft Entourage" to open (every contact whose business
address is {street address:"", city:"", state:"", zip:"", country:""} and
home address is not {street address:"", city:"", state:"", zip:"",
country:""} and default postal address is not home)
-- This script will swap Home & Work addresses for the open contact
(* Swap Home & work addresses v1.0.0
Barry Wainwright 12th August 2003
*)
tell application "Microsoft Entourage"
if class of (get displayed feature of window 1) is contact then
-- a contact window is open
set contactList to {displayed feature of window 1}
else if class of (get displayed feature of window 1) is address book
then
-- address book is open
set contactList to selection
end if
if contactList is {} then
beep
else
repeat with aContact in contactList
tell aContact
copy home address to temp
copy (get business address) to home address
