sockets

[Kenneth Brody]

On 5/15/2012 11:54 AM, Ed Hilovsky wrote:
> The system calls a routine that uses a socket to communicate to the secure
> credit card server. The call routine uses the socketclose statement and then
> closes itself and returns to the main processing. Shouldn't the socket be
> released and able to be used by another user / process ?
[...]

The license info you posted in the other e-mail shows that you only have a 
single socket license.  This means that only one process can use sockets. 
(Though there is no filePro limit on the number of sockets it can use.) 
Another process can't use sockets until that program exits.

-- 
Kenneth Brody