11-20-2009 11:57 AM
11-20-2009 01:51 PM
11-20-2009 02:49 PM
11-20-2009 03:09 PM
11-20-2009 03:57 PM
11-20-2009 04:46 PM
11-21-2009 10:03 AM
If you can update a Contact field from SQ, you could then use ACT!'s Group Membership Rules to add the contacts to the group
If using ACT! 2010, you could use Excel alone via the OLEDB2 interface to get the data. You wouldn't write back to ACT!, but could do the report you need to send directly. See http://blog.glcomputing.com.au/2009/07/connecting-to-act-by-sage-data.html
The OLEDB option prior to ACT! 2010 didn't give access to activities, so if you haven't upgraded, you could try Crystal Clear Essentials from http://www.adsprogramming.com/products.htm - it also doesn't write back to ACT!, but could do the report you need to send directly.
Wondering... if the query fails and you run it again, does it still fail?
As a final option, if you want to send the report with a method above and still note the action in ACT!, you could try bringing the Excel data back (to contacts or groups) with something like itImport
11-21-2009 10:38 AM
11-21-2009 11:05 AM
It sounds possibly like a resource issue...
Might be interesting to look for any messages in the windows Event Viewer on either machine when it fails... or, as it fails with repeated attempts when it does fail, next time run it again and watch the resources with Task Manager or Microsoft's Sysinternals Process Monitor - http://technet.microsoft.com/en-us/sysinternals/bb795533.aspx
If you try these and can see something obvious, please post back... if Sage can't replicate it, it's not easy to fix. But, with the right info, they might figure out the cause.