|
|
Post by nsbrown on Jan 2, 2023 3:13:36 GMT -5
Once and for all, Is there a way to kill basic program even after the error message (OS error 16r57) ?? I mean instead kill the LB process and reload the program and try again ![]() regards, Sharon Brown |
|
|
|
Post by Rod on Jan 2, 2023 9:03:56 GMT -5
The trick would be to avoid generating the error. It is usually associated with files not being available and the solution would be to test for existence before you try and open it. But we need to see your code and your error.log to be sure we know what is going on. Not all the code, just the part where it is failing.
Once the program has crashed there is little you can do. The user needs to use Task Manager to clear out any hung instance of Liberty. So much better to trap or avoid the error in the first place.
|
|
|
|
Post by Walt Decker on Jan 2, 2023 12:17:36 GMT -5
Once and for all, Is there a way to kill basic program even after the error message (OS error 16r57) ?? I mean instead kill the LB process and reload the program and try again ![]() regards, Sharon Brown Ms. Brown, I get that error a great deal along with "index outside of collection bounds". Most of the time I have no idea what the cause is, but it does occur when I use variables to locate controls without going back through and resetting them with a REFRESH instruction.
When it occurs at other times I have to play with the code to see what caused it. Finding it I sometimes then have to re-arrange the code. Other times I have to figure out a work-around.
When it occurs the only way to get out is through task manager.
|
|
