Jim, if you’re calling from the client app (already open) you will not burn another seat. Only if you opened another session would that be the case.
From: jim_chance
Sent: Wednesday, September 28, 2011 10:37 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Epicor licensing
Are we correct in our understanding with regard to Epicor licensing that if the Epicor client app were to call functions from the .dll, we would maintain the current session with Epicor and not cause the license
server to count another license in use as it does now when the .exe is
doing its work?
Epicor licenses are expensive. So, I don't want to use two
licenses to support for one actual user seat, even if it is only a
transient operation.
Otherwise I'd have to convert the app from .exe to .dll to save on the licensing; correct?
[Non-text portions of this message have been removed]
From: jim_chance
Sent: Wednesday, September 28, 2011 10:37 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Epicor licensing
Are we correct in our understanding with regard to Epicor licensing that if the Epicor client app were to call functions from the .dll, we would maintain the current session with Epicor and not cause the license
server to count another license in use as it does now when the .exe is
doing its work?
Epicor licenses are expensive. So, I don't want to use two
licenses to support for one actual user seat, even if it is only a
transient operation.
Otherwise I'd have to convert the app from .exe to .dll to save on the licensing; correct?
[Non-text portions of this message have been removed]