topic Re: Lock Table based on primary key- Problem in executing report in Application Development and Automation Discussions

Lock Table based on primary key- Problem in executing report

Former Member — Wed, 30 Nov 2011 04:21:00 GMT

Hi Experts

In my report we have Personnel no. [pernr-field1] and start work date [field2] on selection screen and both are mandatory.

When one user executes the report with pernr for example as 7 on sel. screen we look the table to update entries.

But if other user at the same time wants to run the report for 1-8 pernr in range he gets a error message that table is locked

this happens because pernr 7 is already locked.

Can anyone suggest how can we avoid this situation ? So that user1 can execute the report for pernr 7

and user2 can execute the report for pernr 1-8

Please share your inputs.

Former Member — Wed, 30 Nov 2011 05:03:01 GMT

I think You have used locking concept in program on database table. remove it your problem will be resolved.

Regards

Ajit

Former Member — Wed, 30 Nov 2011 05:19:38 GMT

Which level of Locking are you using??

Generally lock and unlock on record level should be performed with user action (like save) rather than during life time of report execution.