04-08-2010 08:30 AM
No; to clarify, I have ACT installed on my PC, and the PAD file is sitting on our server (along with the database). The interface I'm trying to create is between ACT (Premium) and our in-house support system.
If it makes any difference, we recently updated our copy of ACT to 11.1, and I'm using the act.framework.dll from that install to ensure that the product versions match - I'm assuming that's the correct thing to do?
04-08-2010 08:47 AM
I believe it uses the licensing service to verify product tier. So it could be that your version isn't registered or that the licensing service isn't running.
04-09-2010 12:35 AM
I've just checked that the product displays as being licensed when I'm actually going into my copy of ACT, and all seems fine there; I presume on that basis that the license server is running okay as well?
As a quick test I've created a local database, imported some contacts and tried connecting to that.
ActFramework actFwk = new ActFramework(); actFwk.LogOn(@"C:\Users\ian.mellett\Documents\ACT\ACT for Windows 11\Databases\ACTPadTest.PAD");
I still get the same issue though.
04-09-2010 02:09 AM
From testing with a local database, I've just noticed that the application Tier appears to be BASIC, which I assume would be the fundamental cause of the issue, but I'm not sure where this would be coming from?
04-09-2010 02:52 AM
I think the bad news is that there is no way around the fact that the Act framework just does not like 64-bit compilation. I can only compile ACT! code on my 64bit machine when I specify x86 as the target CPU.
One possible, and I admit that it is not much of a workaround at all, is to possibly dev on a VM of Win 32bit?
I hope I am wrong and someone can come up with a "magic-bullet" solution!
04-09-2010 02:56 AM
That's the feeling I was starting to get. I *have* got a VM install of Windows XP on here, which I was considering, but that's possibly going to cause complications with it seeing the ACT database on our server due to the network setup.
Thanks for the input though, I might see if there's something else I can do to try and get it into an X86-type environment for the short term at least.
04-09-2010 03:11 AM
04-09-2010 06:33 AM
The ACT .DLL version is 220.127.116.11 and, according to 'about ACT', the current version I'm using (installed on this PC) is:
ACT! by Sage Premium 2009 (11.0) Version 18.104.22.168, Hotfix 4
This is running in C# express on a Win7, 64bit, so I can't target specific CPUs.
Anybody got any clues to point me in the right direction?
May i recomment right-clickign your project and selecting properties. On the build tab, about 1/4 of the way down in the "General" section is a platform target dropdown. It's my interpretation that you're saying you can't select x86 from the top drop-downs.
If it's not saving, make sure (that for any reason) your directory/solution files are not red-only protected.