08-12-2015 06:58 AM - edited 08-12-2015 06:59 AM
I am having the exact same problem Mike. This is a pretty big deal and you would think ACT would be responding with more effort.
Not only can I not add documents but every time I click on the documents tab, ACT crashes.
08-12-2015 07:30 AM
I ended up having to down rev windows to 8.1. It is pretty simple just go to SETTINGS -> UPDATE & SECURITY -> RECOVERY -> GO BACK TO WINDOWS 7 OR 8. It takes about 15 minutes and saves all the configured settings you already setup. Tested both attaching files to ACT and upon exit, no error message.
08-12-2015 01:58 PM
08-12-2015 05:05 PM
Small point but worth noting ...
I don't believe that Microsoft have stated that MS SQL 2008 or 200 R2 are not compatible with Windows 10 but they do say that this version of MS SQL is not supported on Windows 10. There is a difference, refer https://support.microsoft.com/en-us/kb/2681562
08-13-2015 03:01 AM
When I synchronize contact with outlook and select all contact OK
If I use synch set I cann see the number of contact to be synchr but no contact are syncchronize, no error message and the report just shown 0
what to do
08-13-2015 11:57 AM
I have Act 2011 Pro and when I upgraded from Windows 7 to Windows 10, I began getting an error message when I close the app -- "Object reference not set to an instance of an object." The app works ok under Windows 10 (I had already right-clicked the app on the desktop and run the "compatibility" tool to eliminate another issue. But I still have this problem). Can anyone provide a suggested fix?
08-14-2015 09:46 AM
We are working to bring our current version of Act! along with future releases compatible with Microsoft 10. To track known issues, questions and compatibility please check the Knowledgebase articles listed below.
Is Act! compatible with Windows® 10? http://kb.swiftpage.com/app/answers/detail/a_id/38167/kw/windows%2010
What are the known issues and workarounds for using Act! v17 and later with Windows 10
What are the best practices for using Act! with Windows 10
08-14-2015 09:57 AM
As I previously posted, I see the same error with Pro 2013 but the error appears harmless. I'm glad to see you are working on Windows 10 issues. Not long ago I got a mailing from sales saying a special upgrade price was available until mid-September. I really don't want to upgrade until you fix all of the Windows 10 issues and I doubt I'm alone at that. I hope you will rethink the end of the upgrade special and make it available after you have a Windows 10 compatible version.