Crashing

[Mike Matthews - Omnis]

Hello Das,

On a similar note, I put a 2-3 second wait after a Working Message, and before I issue another command, eg, FileOps.$copyFile.  Without it, the working message just doesn’t show up, annoying for the user.  So just wait a few seconds, and all is good.

I didn’t know about the sleep() function either.

Mike Matthews

Lineal Software Solutions
Commercial House, The Strand<x-apple-data-detectors://1/1> Barnstaple, Devon, EX31 1EU<x-apple-data-detectors://1/1>

omnis at lineal.co.uk<mailto:mike.matthews at lineal.co.uk>

www.lineal.co.uk<http://www.lineal.co.uk/>

www.sqlworks.co.uk<http://www.sqlworks.co/>



On 5 Dec 2022, at 18:44, Das Goravani <goravanis at gmail.com<mailto:goravanis at gmail.com>> wrote:

Caution: This is a message which has originated from outside the organisation. Ensure the sender is trusted and the content is safe before opening links or attachments.



The inserting of

Sleep(100) has made the crashing stop as Max recommended.

Max, there is the function sleep() where you put in 1000’s of a second amount you want to sleep for..

This immediately stopped my SQL workers from crashing, though it added 2.5 seconds to my load since there’s 25 iterations

That’s fine, 2.5 seconds to not crash.. is worth it.

Now I can move on to perfecting all things.

Yay

Thanks Max H.
_____________________________________________________________
Manage your list subscriptions at https://lists.omnis-dev.com
Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com