06-11-2015 02:46 PM
This error occurs whenever the user tries to edit the Company field in an Act! v17.1 Pro database (MSSQL 2012 64bit installed on a Win 2012 Server 64bit) recently upgraded from Act! 2000. There might be a linkage to Handheld Contact but not sure at this stage. The DB seemed ok to start with, but then the problem developed very quickly. I created a copy of the DB & that tested ok. Then reconfigured HHC to work with the new DB & initiated the sync. The error manifested itself immediately. But as I say, I am not sure if there is a relationship with HHC. It is the first time I have installed Act! with MSSQL 2012 + HHC. Any help appreciated.
06-11-2015 05:47 PM
A corection to my previous post. MSSQL 2014 was installed, not MSSQL 2012.
06-19-2015 03:31 AM
i i have the exact same issue with Premium 17.1
its not possible to link a contact to an existing company.
HHC is not installed. (123sync is )
SQL 2014 express is used
06-19-2015 03:39 AM
created a copy of the database
first time logged in i was able to add a contact to company
logged of and back in and unfortunately the same error again
06-19-2015 05:13 AM
We have the same issue in a client implementation (Act! Premium 17,1 on SQL 2014 Express). Error is occuring on server and RDBs on Win 7 and Win 8 laptops with SQL 2014 Express. Brand new database (one addon installed - Exponenciel's Excel Quote/Invoice Maker II). Tried recreating the publisher (save copy as) and rebuilding RDBs - no joy.
Demo database appears to fucntion correctly. All ACTDIAG stuff run. Swiftpage support (UK) arent aware of this and have recommended database rebuild (which would be OK if it werent already a brand new database).
06-19-2015 09:33 AM
I'm wondering if this is an issue with a linked field and the Company field that the Contact field is linked to doesn't allow nulls? Just a wild guess.
06-19-2015 10:06 AM
Thanks Stan - rational guess (and I appreciate your time) but I've narrowed it down to 'Company Preferences'...
If Company Creation threshold is set to anything other than '0', the problem manifests itself.
By resetting to '0', the problem goes away, so at least I have a workaround in the short term.
There's still some underlying issue here though. I have no mandatory fields in my database - either in the Contact or Company entity. The only Linked Fields are the default ones. There are no custom fields in the Company entity (just a couple in the Contact entity).
I've tested this again in the Demo DB and that doesnt exhibit the same symptoms (even with Company Creation enabled).
Could be a bug I guess.
06-19-2015 10:13 AM
Are there values in the default sorting list for Companies?
06-19-2015 10:20 AM
06-19-2015 10:52 AM
Oh well. Just a stab in the dark. Act! Development is looking into the issue. Hopefully they'll have a fix soon.