Locking problem with Oralce 9i/PowerHouse

[Frank Huizinga]

Hi,

The problem is that I have a screen with just one file declared as primary
and the Nocommit option applied to the screen statement, when two or more
users are running this screen and one of them does an update the other ones
are locked as long as the transaction has not been committed or rollbacked
by the first user.

How can I avoid users from being locked and still use the Nocommit option on
the screen statement.

Sample:

Screen X Nocommit

File DAILY_RENTAL In AL_DB Primary

Generate


Thanks, Frank