Hi All,
Just discovered this forum. Looks like a very good resource.
I have a client that is moving from 5.0A to 5.1 of AccPac for Windows soon. Question: are there any known changes/issues/problems with any VB code that is using the API via A4wcom.dll? I wrote a VB COM wrapper that allows them to create AP/AR invoices from their custom business app. We are not an AccPac reseller so we don't have any way to test the upgrade offline. I'm not sure how familiar their reseller is with this type of integration. They had been trying to push us to do an export/import process. The API is so much cleaner and is very seamless to the end-user. I just want some assurance that the 5.1 upgrade isn't going to "break" anything on the client side.
Also, an unrelated question: when we went live with this integration, we discovered that only 1 user could successfully connect at a time through the API. Is there any way around this? I think their reseller said there would need to be some additional API licenses purchased, or something in that regard. Or, is this some type of "blocking" occurring since the DLL that I have that wraps A4wcom.dll is shared on a network drive?
Thanks for any and all help.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Randy Jean, MCP, Integration Services
Orion Group Software Engineers
Just discovered this forum. Looks like a very good resource.
I have a client that is moving from 5.0A to 5.1 of AccPac for Windows soon. Question: are there any known changes/issues/problems with any VB code that is using the API via A4wcom.dll? I wrote a VB COM wrapper that allows them to create AP/AR invoices from their custom business app. We are not an AccPac reseller so we don't have any way to test the upgrade offline. I'm not sure how familiar their reseller is with this type of integration. They had been trying to push us to do an export/import process. The API is so much cleaner and is very seamless to the end-user. I just want some assurance that the 5.1 upgrade isn't going to "break" anything on the client side.
Also, an unrelated question: when we went live with this integration, we discovered that only 1 user could successfully connect at a time through the API. Is there any way around this? I think their reseller said there would need to be some additional API licenses purchased, or something in that regard. Or, is this some type of "blocking" occurring since the DLL that I have that wraps A4wcom.dll is shared on a network drive?
Thanks for any and all help.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Randy Jean, MCP, Integration Services
Orion Group Software Engineers