09-15-2011 12:03 PM
We have an in-house manufacturing management system created in Access 2007, and are also using Act! 2010 for our CRM. We would like to be able to draw in the current contact from Act! into our Access database. This is a one way transfer (eg from Act! to Access).
Can someone provide some advise on the best way to do this? I have seen a number of 3rd party apps that do this (Quotewerks is a good example).
09-15-2011 12:20 PM
09-16-2011 10:51 AM
I'm a consultant working on this issue for my client. I have chatted with technical support and they have told me that we are not able to connect/read the ACT! Pro database through ODBC or OLEDB. We must upgrade to premium or buy the SA password.
Is this your understanding as well?
I'm currenty trying to get in touch with your SDK team to see what options I have there...
09-16-2011 10:11 PM
09-17-2011 09:43 AM
Thanks for the reply Mike.
Can you give me so more info on using OLEDB to connect to the ACT! database. I can certainly see how it's done in Excel or other Office documents but I don't believe this can be done from MS Access. If you know how to do this can you give me the details?
The same goes for the SDK. I'm unclear how you can use the info from the SDK to make a connection to the ACT! database from MS Access. Best case scenario won't you still need the SA password?
09-17-2011 08:18 PM
09-19-2011 11:27 AM
I think you may be incorrect there Mike - in previous versions of MS Access you could setup an ODBC connection to other data sources, but an OLEDB link from inside of MS ACCESS to other data sources was not supported.
You can, of course, access your MS ACCESS data via an OLEDB driver.
09-19-2011 12:29 PM
Thanks for your responses. I'm still unsure where we stand on this issue. The goal is to access the Pro version of Act! database from an MS Access database.
MS Access does not work with OLEDB as easily as it does ODBC but in any case, creating an OLEDB connection will still require authentication to the ACT! database correct? Either way we'll still need the SA password to make the connection.
Unless there is an OLEDB driver for the Pro version but I don't think there is.
Mike, don't we have the same issue when using .Net to make a connection to the Act! database? We still need to authenticate and the Pro version of Act! doesn't come with any kind of authentication mechanism.
Can either of you shed any light on these questions?
09-20-2011 01:08 AM
I thought I would just pipe in here.
To use the SDK you'll need to code in .NET. Unfortunately I think VBA is not .NET so the way around this would be to create an "adaptor" class in .NET 3.5 or 2.0 that has public methods and to ensure that this dll class when compiled is COM exposed. YOu can then bring this class into your mdb project as a module (I think). This is all fairly simple stuff and a simple google will show you how to compile a COM .NET dll. If not come back here and we can walk you through it.
Connections to the ACT! dB are fairly trivial bits of code:
ActFramework oFram = new ActFramework(); //new instanace of the ACT! framework
...and that's it your logged in!
If your connecting via the application model then its even simpler since you don't need to authenticate since your already logged into ACT! You just need a running instance of the ActApplication object which is equally as trivial!
P.S. the same SDK code works for both Pro and Premium editions.