03-14-2017 09:50 AM
Thank you for your reply Gary. I did get it to work, but it is so slow that it is really not functional. I don't know if this is because I have not upgraded to the latest version. Is this possible? Are there any other issues with upgrading. This issue has already hurt enough and I don't have time to fix any additional problems.
03-14-2017 09:59 AM
03-14-2017 10:06 AM
I think memory is ok. This is a fairly new machine with 16B RAM. I've attached a screenshot of task manager below.
I really don't think anything on my end has changed since I was last using ACT between Christmas and New Years.
Thanks again for your help.
03-14-2017 12:15 PM
Nope. Slowness from the start. Slower as resources come up. Like I said, for some reason, one of the act developers or product directors got the insane idea of using some obscure embedded browser instead of using google. Now we have to live with their bad decisions.
03-15-2017 03:41 AM
How slow are we talking about here? It would be useful if you could give us some benchmark figures from the web info tab, i.e:
For reference, Act! uses the .NET WebBrowser control, which is a wrapper for IE that uses the same components already installed on the client machine. I believe the Product Development will be researching improvements to this area for future versions of the software as part of the defect I posted earlier.
03-15-2017 04:58 AM
30 seconds to never. Pages are partially loading. LinkedIn has never worked properly in the Act windows. So many problems with it, it's not worth ever detailing them all. Core of the problem is that Act should replace the foundation of the web access. But since the company can't even get a minor browser linked changed in the space of 3-4 months, there's no since hoping that the entire flawed browser architecture could get changed over.