Changing AccpacCOMAPI to AccpacxApi

[Trac12]

Hi Guys, I was wondering if anyone can please help me. We have developed a program using VB and C#. We have originally designed it using AccpacCOMAPI in the macro's, but now we want to change it to AccpacxApi.
Trying to create the session seems to be a problem. This is the syntax that I used:
Session = New xapiSession
Session = CreateObject("ACCPAC.xapisession")
Session.Open(Username, Password, Database, DateTime.Now, 0)

I have imported the namespace: Imports ACCPACXAPILib
and declared the variable: Public Session As ACCPACXAPILib.xapiSession

Any help on the above would be greatly appreciated.

 

[ettienne]

Geez why? XAPI is old and has been replaced by AccpacCOMAPI.

 

[ettienne]

Don't get me wrong, if you really want to do that then its fine. You just need to be doing it for the right reason, so what is the reason?

 

[Trac12]

Hi ettienne, we are trying to get away from COMAPI at the moment.

 

[ettienne]

Why? You can do more with COMAPI than you can with XAPI. There has to be a better reason than that. I have been programming with Accpac for 20+ years, I'm not new at this, so that's why I'm intrigued..... I might learn something new

 

[Trac12]

Hi Ettiene
The COMAPI uses Lanpac licence which causes issues on our API at our client hence why we want to use Xapi.

 

[ettienne]

Haha, that's not true. Whoever told you that is lying. XAPI still consumes a lanpak, just like everything else. The licensing was changed in recent versions and XAPI now does use a lanpak.

 

[ettienne]

There is another license called an Integration Access Pack (IAP) - don't fall for that one either. IAPs have been discontinued in recent versions and are no longer applicable - but Sage will gladly sell you some without teling you they don't work anymore.
Why do I know this? We went through this whole scenario with a client developing add-on software and they were running into the same lanpak issue. After a lot of back and forth between Sage, us and the client and in the end Sage came up red faced and admitted that XAPI and IAP are no longer supported.

 

[Trac12]

Hi Ettienne,
Thank you for your help thus far.
What was your resolution to this problem?
Is there any other way to integrate third party software directly into Accpac without utilising a license?

 

[DjangMan]

Plus the licensing has changed with version 2012. Each workstation will consume only 1 lanpak no matter how many times it is logged into Accpac Sage ERP 300.

If switching over to the XAPI will take you 10-20 hours of labour then just sell the client a lanpak if they are worried about using up licenses (prior to 2012).

 

[ettienne]

There is no problem. If you integrate anything to Sage Accpac then it will use a license, that is what the Sage Accpac software license agreement is about and it is a fact of life.
In this client's case they changed their software to batch all transactions and have one server connection to Accpac consuming one license. Previously they had 50+ users each connecting to Accpac contending for 20 available licenses, not a viable solution.