10-20-2019, 08:21 PM
I have an application that locks up- sometimes for a minute or two and other times to the point of crashing the application altogether.
The only error that I can trap is a tsnet error (6).
I can only track this in the runtime mode and only using the message box.
there are other messages but they are overridden by the above error.
Is there a way to trap these errors and save them for analysis?
I do admit that I hit a button to refresh my data often to create this problem but this is a typical uses case for some applications.
Sometimes the error occurs just after the application may is idle for a bit before requesting an update.
is there a way to change the tsnet parameters to let tsnet catch up?
we might want to do a TEAMS session so that you can witness this for yourself.
The only error that I can trap is a tsnet error (6).
I can only track this in the runtime mode and only using the message box.
there are other messages but they are overridden by the above error.
Is there a way to trap these errors and save them for analysis?
I do admit that I hit a button to refresh my data often to create this problem but this is a typical uses case for some applications.
Sometimes the error occurs just after the application may is idle for a bit before requesting an update.
is there a way to change the tsnet parameters to let tsnet catch up?
we might want to do a TEAMS session so that you can witness this for yourself.