7 replies to this topic

[mdexter]

Has anyone had any luck showing useful record lock information in UMSG's? Here's my specific case. I have any update function with lock logic on a table. When a lock is encountered, the function reads a record showing who's got the record locked. I would like to display this information to the user who is locked (e.g., in a UMSG) without interfering with the processing.

The only method I have found that works at all is to do a UMSG ($$MSG,5), which displays the message for 5 seconds. Then the message is replaced by the "RECORD LOCKED - WAITING" message, which is then replaced by "UPDATE IN PROGRESS - PLEASE WAIT". If the lock persists, the cycle is "UPDATE IN PROGRESS" followed by my message for 5 seconds, followed by "RECORD LOCKED" for a couple of seconds.

It would be nice to be able to control the "UPDATE IN PROGRESS" message that automatically appears when PRO-IV retries the file read. Does anyone have any ideas about how one might do this? Thanks. Mark Dexter

[George Macken]

I have not implemented the following suggestion

could you call a global screen (probably not a window) which displays who is locking the record - that this is a global screen - not Clearing the screen - painting the required screen fields in a location on screen - ONE TIME LS - Disable PRO-IV Rtn to continue

hope this helps

Rgds

George

[Rob Donovan]

Hi,

You can set the 'Suppress Msg' flag to 'Y' for the function, and this will stop the 'UPDATE IN PROGRESS' message from being displayed.

Rob D.

[mdexter]

Rob, thanks for the tip about suppressing the update message. Unfortunately, that doesn't work in this case. Basically, the "RECORD LOCKED - WAITING" message still wipes out my UMSG and I can't see any way to re-display a UMSG after that. It doesn't appear to re-visit the logic before in the timing cycle, so I can't see how to put in a logic. Mark

[Rob Donovan]

Ok,

Then also try using a MSG instead of a UMSG, that should stop the standard record locked message.

It worked in my test function, but I'm not sure if it will in your function...

Rob D.

[mdexter]

Rob, thanks for the idea. Unfortunately, this stops the update until the user presses return, same as a UMSG('test',-1). I don't want the update paused but just want the user to be able to see what is happening. Mark

[Rob Donovan]

Hi,

Thats strange, it doesnt do that in my function.

A MSG in an update function has always just displayed a message and then continues with no keyboard input.

Once the reocrd lock has gone, then the update will continue to run, but it will still display your 'RECORD IS LOCKED' MSG... is that it??

If so, you need to set a flag in Lock logic, and then in ARNE you need to do another MSG to display something more appropriate (and reset the flag).

Or maybe there is something different with your version.

I'm testing with Windows XP, 5.5r333

Rob D

[Kevin Bruss]

Maybe just try a 1 second delay UMSG like:

UMSG($TABLE + ' Table locked by ' + $LOCKUSER,1)
it would display it for a little bit, but not have to wait for the user..
it would also potentially keep the client from hammering the database waiting for the lock to clear.

I'm not savvy with the use of locking logic, but could you perform the write in an lscall and bail on each lock (then return via while loop) ? this might help control the output on the bottom of the screen. Perhaps you can even set it so that it technically doesnt process a lock cycle; just exit back if locked and then you don't get the "RECORD LOCKED PLEASE WAIT" message..?

Just an idea... HTH
-Kevin