JohnDanter2
VIP Member
Hi folks,
I think I know the answer to this before typing this but just want to double check.
Am I right in thinking, E1 screens do not lock any database records themselves at all? (or does it depend on your database? - we use Oracle)
It may occur for a split second in the OK button, but the screens themselves do not do anything special. BSFNS may do this using the select for update APIs etc, but screens in general do not form any lock what so ever.
If they did, they F00095 would not need to be created. Am I right with these assumptions?
Only reason I ask I've been asked to test a delete/purge UBE informs a user a record cannot be purged as someone is in the screen (locked the record)
but I tested this a few times yesterday and my delete statement (table IO) works fine and SV File IO is success afterwards.
So it looks like I've no way way of knowing someone maybe viewing for update a F41021 record.
Thanks
John
I think I know the answer to this before typing this but just want to double check.
Am I right in thinking, E1 screens do not lock any database records themselves at all? (or does it depend on your database? - we use Oracle)
It may occur for a split second in the OK button, but the screens themselves do not do anything special. BSFNS may do this using the select for update APIs etc, but screens in general do not form any lock what so ever.
If they did, they F00095 would not need to be created. Am I right with these assumptions?
Only reason I ask I've been asked to test a delete/purge UBE informs a user a record cannot be purged as someone is in the screen (locked the record)
but I tested this a few times yesterday and my delete statement (table IO) works fine and SV File IO is success afterwards.
So it looks like I've no way way of knowing someone maybe viewing for update a F41021 record.
Thanks
John