07-31-2017 05:09 AM
Assuming you are running the UK version of Act! (You can confirm in Help > About Act!) and have Office 2010 installed and ready to go.
Simply download and install this SP2 update, then after that's done, install this hotfix update. You can then open Act! and check the integration, and mail merge away.
08-08-2017 06:44 PM
We were consulting with an external Microsoft Office specialist on this defect last week, and gained some new leads to follow up around potential solutions. Our development team are reviewing these now, and I'm hoping to have confirmation on how we can fix it and the scope of the work by the end of the week.
Obviously the ideal output of this is a solution we can roll up into a hotfix package, similar to the fix deployed for Office 2010 users. The above work will confirm whether this is possible, or not. Either way, I'll provide full details of our findings here as soon as I have them.
Another month gone by with this issue and Outlook 2016 ...
Please update on the consultation, review and scoping you referred to. As indicated this would have taken place some 3 weeks ago. What are the findings?
08-09-2017 07:43 AM
Thank you for the prompt Graeme,
As mentioned above, our development team have been following up on several new potential solutions to this issue for Office 2013 and 2016 users. This research took a little longer than expected, but I had hoped to get our findings shared earlier this week.
Despite the additional development time and resources dedicated to this issue, sadly we do not have a solution we can implement until after our v20 release later this year. The only way forward remains a full re-write of the mail merge feature. As some added complexity to this, a re-write is also more involved than we initially thought, and is a risk to other Office integration functionality due to a number of shared components. The result is unfortunately a significantly bigger development task to be planned in to an upcoming Act! release.
This is certainly not the update I wanted to deliver to everyone, and I appreciate it will be frustrating news. We do however remain committed to resolving the issue as soon as a re-write can be scheduled in. We are conducting planning sessions across this month for a number of future releases and updates, so I'll provide a more detailed timescale for this work as soon as I possibly can.
08-09-2017 02:34 PM
Stuart, so you expect everyone who purchased Act v19 which turned out to be a dud which clearly is a product that hasn’t worked properly from day one to happily comply with Swiftpage and spend more of our hard earned money on Act v20 as version 20 will supposedly have all the fixes that will make Act a fullly functioning product?
Act v19 should not have been released in the first place, it is clearly a product that is NOT FIT FOR PURPOSE!
Apart from the mail merge issues which are clearly in abundance there’s also the issue that Act v19 doesn’t work with the 64bit version of MS Office 2016 which is contrary to the advertising that Swiftpage put out on the Act website!
How do you honestly expect all your customers to purchase an upgrade to Act v20 when we have so little faith in a product that hasn’t worked properly since its release?
08-09-2017 02:47 PM
I'm sure Stuart will respond tomorrow when he is back in the office.
Have you considered using Act! E-Marketing?
I was in the very position you are 2 weeks ago with the same feelings and concerns. A few phone calls later with Stuart and his team and we are now working around the problem with a temporary solution. I have to point out that changes made in Office by Microsoft are the root cause to the issues most users are now experiencing in Act!
When v19 was released it worked perfectly with Office 2010 and 2016 both in 32bit and 64bit, a few windows updates later and slowly more and more features stopped working. Most have now been resolved as far as I know. The major one left outstanding is this one, images in mail merges.
Hopefully Stuart and his team can help yourself and your users move forward in the way that they have done with us.
08-09-2017 02:55 PM
The point is that Act v19 is not fit for purpose! So many people have lost faith in Swiftpage and have (or about to) switch to a competitor product.
Now they expect us to pay for the upgraded v20 which (if we are to believe their claims) will fix the issues that have plagued Act v19.
By forcing people to pay for a version of Act that is supposedly going to work is not good customer practise. Swiftpage needs to fix Act v19
08-09-2017 02:59 PM
Cant say that I have seen anywhere that they will forcing payment for the upgrade.
I personally know how serious Stuart and his team are taking this issue.
I first came to the community forums ranting about the unknowns, I suggest contacting swiftpage and speaking with them you may be surprised how willing they are to help!
08-09-2017 05:26 PM - edited 08-09-2017 11:09 PM
If they are not going to fix Act V19 to that of a fully functioning working product as the advertising claims then as Stuart clearly says in his post above "Despite the additional development time and resources dedicated to this issue, sadly we do not have a solution we can implement until after our v20 release later this year."
That in my book says to get Act v19 working then we need to upgrade to Act v20! That clearly is forcing me to spend more money on a product that we don't know for sure will work with MS Office 2016....