Unable to type after selecting contact from Address Book

[Joe Grover]

I have a user that has an odd problem. When creating a new message and
clicking the To: button to open the Address Book and selecting a Contact,
they are unable to type any further data once the contact has been pulled
into the To: field (unable to type a Subject, type anything in the To: or
Cc: fields, etc). They can only tab around between the fields. This does
*not* happen if they open their address book from the Tools menu, select a
contact, and go to File -> New Message. They also do not have this problem
if they manually type in an email address, or type enough for the nick cache
to kick in and autocomplete for them.

Anyone have any ideas what could cause this? Thanks in advance.

Joe

 

[Joe Grover]

Addendum:

- This is an Outlook 2003 client connecting to an Exchange 2003 server.
- It is the only user experiencing the problem.
- It happens whether the contact was pulled from the Global Address List or
the user's personal Contacts.
- I just switched the mail editor to use Word and the problem goes away,
however the user does not want Word as the editor.
- It works fine on another machine logged in as the same user (and not using
Word as the editor).

If there's a way to eliminate this problem without forcing the user to
switch to Word as the editor, I'm all...um...eyes.

Joe

 

[Russ Valentine [MVP-Outlook]]

Have you tried removing the Outlook Address Book Service from the profile,
restarting Outlook, then re-adding it?

 

[Joe Grover]

That appears to have done the trick. Thanks Russ!

Joe

Have you tried removing the Outlook Address Book Service from the profile,
restarting Outlook, then re-adding it?
--
Russ Valentine
[MVP-Outlook]

Addendum:

- This is an Outlook 2003 client connecting to an Exchange 2003 server.
- It is the only user experiencing the problem.
- It happens whether the contact was pulled from the Global Address List
or the user's personal Contacts.
- I just switched the mail editor to use Word and the problem goes away,
however the user does not want Word as the editor.
- It works fine on another machine logged in as the same user (and not
using Word as the editor).

If there's a way to eliminate this problem without forcing the user to
switch to Word as the editor, I'm all...um...eyes.

Joe