I have a procedure, which I will call A, made in Microsoft Access environment that I use as a socket server, uses the MsWinsck.ocx control
A second procedure, which I will call B, also implemented in Access, which is used to send information to procedure A
I would like to replace procedure B with a program, which I will call D, made in B4J because I believe it has better functionality
I then wrote program D in B4J code to perform the same operations that were previously performed by B
Program D connects successfully to server A, sends data, disconnects and reconnects successfully
There is only one difference with the original program B and it is the inability of server A to 'hear' the disconnection
When program D is shut down abruptly, for example using the Windows task manager, server A does not 'hear' the disconnection of client D
And this anomaly is particularly serious because it prevents the server from accepting subsequent reconnections from client D
Keeping the connection open is necessary because even the server can return information to the client and therefore it is not possible for me, client side, to open a connection, send information, and close
This is a video that allows you to quickly understand what I am requesting
In attach the sources of program A, B, D
So the question is: what are the differences between the socket / jnetwork library compared to the MsWinsck.ocx and how to make the server 'hear' the interruption of the connection (like using Microsoft Access client, program B)
A second procedure, which I will call B, also implemented in Access, which is used to send information to procedure A
I would like to replace procedure B with a program, which I will call D, made in B4J because I believe it has better functionality
I then wrote program D in B4J code to perform the same operations that were previously performed by B
Program D connects successfully to server A, sends data, disconnects and reconnects successfully
There is only one difference with the original program B and it is the inability of server A to 'hear' the disconnection
When program D is shut down abruptly, for example using the Windows task manager, server A does not 'hear' the disconnection of client D
And this anomaly is particularly serious because it prevents the server from accepting subsequent reconnections from client D
Keeping the connection open is necessary because even the server can return information to the client and therefore it is not possible for me, client side, to open a connection, send information, and close
This is a video that allows you to quickly understand what I am requesting
In attach the sources of program A, B, D
So the question is: what are the differences between the socket / jnetwork library compared to the MsWinsck.ocx and how to make the server 'hear' the interruption of the connection (like using Microsoft Access client, program B)