It suggests setting a timeout to wait a while until the db is hopefully unlocked or using the ‘busy’ method but it doesn’t give any examples. Is this where the catch command comes in?
That did occur to me so instead I’ve put in the line ‘db timeout 2000’ which, according to the documentation, should retry for 2 seconds during which time hopefully the database should no longer be locked. It seems the safer option as it’s a live ordercomms interface.
It’s worked ok as I haven’t had any ‘database locked’ errors with the code I’ve implemented it in. I have had the problem arise with other procs so you’ve prompted me to make the changes elsewhere.
Thanks,
Dave
Author
Replies
Viewing 8 reply threads
The forum ‘Cloverleaf’ is closed to new topics and replies.