Hi All
I eventually found out why the timer procedure is bombing out. After not writing to MyTable for a length of time, in other words, it is idle on the MySQL side so I suspect the channel is being closed, I get the error below:
//native MySQL access error.
//Unable to open or read <MyTable> file.
//Error Number = 22
//The following error was returned by the <123.123.123.123> database:
//Error number = <2006>.
//Error message:
//MySQL server has gone away - Failed To Reset MyTable
This happens on an HReset(MyTable)
I am confused as HOpenConnection returns true. I am going to try and open the connection in this procedure if any writing is to be done or ignore it. And close it when leaving the procedure if it was opened.
Any other ideas?
Cheers
André
I eventually found out why the timer procedure is bombing out. After not writing to MyTable for a length of time, in other words, it is idle on the MySQL side so I suspect the channel is being closed, I get the error below:
//native MySQL access error.
//Unable to open or read <MyTable> file.
//Error Number = 22
//The following error was returned by the <123.123.123.123> database:
//Error number = <2006>.
//Error message:
//MySQL server has gone away - Failed To Reset MyTable
This happens on an HReset(MyTable)
I am confused as HOpenConnection returns true. I am going to try and open the connection in this procedure if any writing is to be done or ignore it. And close it when leaving the procedure if it was opened.
Any other ideas?
Cheers
André