FJ Software

Whenever I syncronise the phone's Contacts (HTC Desire Z) with Outlook 2003 on my workplace PC it changes my area code (which should be blank in Denmark). After sync the area Code is = 0000.
All new contacts I add in Outlook will then have this area code within brackets, for all the contact's phone numbers.

I can change it back in Outlook via [Tools] - [Send/receive] - [Dial-up connection] - [Location settings . .], by adding a new location with a blank area code. But next time I syncronise, this new location is also changed to 0000

Any fix available ?

Br.
Poul

This is already a fix to avoid that Outlook removes the + prefix on sync

This fix results in useless telephone numbers on my phone. How can that be a fix?

What the area code does is:
If the telephone number should be +45 1234 5678
When inserting it in Outlook it becomes: +45 (0000) 1234 5678
After sync it becomes (on the phone): +45000012345678

And that telephone number is useless.

Br. Poul

PS: My phone is a HTC Desire Z

I have this workaround included since 2 years and i never heard that it makes problems. You are the first user with this problem so i think there must be a setting which is enabled only on your PC.
If you do not find a fix then you could set the access to the following Registry-Key to Admin-Only:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Telephony\Locations

Hi There

I have the exact same issue as Tyrrell. When using MPE, it always changes my Location settings to Area Code = 0000 resulting in false telephone numbers for new contacts in Outlook, eg. +45 0000 12345678.

Since there is no Area Code in Danish Telephone numbers, the above adding of area code 0000 will render the number invalid and thus can not be dialed.

Any plans for a fix, please?

Hey there all

I am sooo happy to have found this wonderful little program, but really sad that all NEW phone entries I create suffer from the area code prefix of 0000.

Yes, I am in Denmark too.

I run Windows 7 Ultimate 64 bit, and Outlook 2010.

Did anybody find a work-around or a fix to this issue?

All the best,
Mark

OK, i did a review again and i changed the behaviour. In the next update the problem will be fixed

Thank you! By the way, I found a manual work around, but I'm looking forward to the update...