09-05-2011 10:02 AM
I'm sure this has been answered 100 times, but I cannot find it easily in documentation. I am working in EXCEL VBA and simply want to connect to ACT 2011 to find the current contact and get basic information (name, address, etc) about that contact. How can I do this?
Not just accessing the OLEDB database, because I do need to know the contact the user is currently showing in the UI.
09-05-2011 02:00 PM
09-06-2011 05:41 AM
That's a shame, because older versions of ACT could do it, and now my client is stuck. I did see mention of the OLEDB provider and connecting to the framework. Would that do it? Or is my only possiblity to connect to the database (and there is so much banter back and forth on the correct format of that connection string - is it documented cleanly somewhere) and then list all the contacts so the user has to [re-] select the active client so I can get the relevant contact information?
09-06-2011 07:07 AM
The provider could deliver reporting data, but wouldn't be able to tell you things in the context of the application, such as the current contact. The only avenue to that sort of information is via the SDK and developing a plugin.
09-06-2011 08:58 AM
All of our add-on products can be found in our store. If you don't find something that meets your needs there are some folks here who do custom applicationd development.
09-06-2011 01:58 PM
09-06-2011 02:10 PM
At a minimum:
I have a Excel VBA application that generates quotes It needs to go out to ACT! to get the current contact's basic information (name, address, phone, and email) so it can place it on the quote.
In older versions of ACT I alo placed the generated excel workbook on the linked documents tab and created a history entry for the quote. Those aren't essential, tho the linked document is very helpful.
09-06-2011 02:15 PM
You could try something simple as per this ACT! Knowledge Base article -
Or something like QuoteMaker:
09-06-2011 03:24 PM
Solution 1 does not cut it - too many manual steps that mu customer's employees will do wrong and will interfere with all the automation I've already cut it
Solution 2 is an old time competitior (10 years ago I was in the quoting business; this current customer has used my product with ACT for 12 years and is now moving away from the older versions)
Looks like I'll have to find someone to write the interface that I will need - basically just emulating good old fashion DDE or simple OLE Automation from the old days. When things were simpler...