Community
Showing results for 
Search instead for 
Do you mean 
Reply

Outlook slows considerably when opening address book.

New Member
Posts: 18
Country: United States

Re: Outlook slows considerably when opening address book.

It's a random issue.  We have two computers here running the same Act version, Outlook 2016 and Win 10.  One computer runs absolutely fine.  Address book and emails work just fine.  The other takes 5-10 minutes just to load the address book and then another two to three once the email is sent.

New Member
Posts: 3
Country: USA

Re: Outlook slows considerably when opening address book.

Good to know.  Was one an upgrade to Windows 10 and the other preinstalled on a new machine? Have you given up and just going to live with it or are you still trying to make it work?

New Member
Posts: 18
Country: United States

Re: Outlook slows considerably when opening address book.

[ Edited ]

They were both new computers - granted they're two different brands, but why would that make a difference. Right now we're living with it, but if this isn't corrected, we will be looking at moving to a different product to use. It's a shame though. Been using ACT! since 1999, and while it's had it's share of glitches, a major one like this was corrected MUCH faster in the past.

Administrator
Posts: 1,372
Country: United_Kingdom

Re: Outlook slows considerably when opening address book.

This issue is still being looked at, due to a few issues integrating with the latest versions of Outlook the developers are in the process of rewriting the integration service from the ground up.

Essentially, the core of the way Act! and Outlook integrate together has been unchanged for a long time. However, recently Microsoft have started to change the way they want other programs to integrate, and so the old methods are slowly beginning to depreciate. There's a lot of development time and effort going into integration with Office at the moment.

I don't have specific details on what bugs are being addressed, but I do know that this issue is a common complaint for a lot of our users - so it's certainly on the radar for a fix in upcoming releases.