While I'm not a PowerBuilder developer, I would assume there is some way in
PowerBuilder to set the connection/recordset to use optimistic or batch
locking.
Failing that, modify the application to use a disconnected recordset.
This is really an application design issue more than a SQL Server
programming issue.
This is, of course, assuming that you _want_ to allow that user to edit the
table directly. If not, do as Uri suggested and look into the KILL command.
Optionally, you could give the user a good swift kick and explain to them
that they are causing application failures across the system. If you take
this option, make sure you make the statement within earshot of the
CTO/COO/CEO for maximum effectiveness.
--
Toby Herring
Software Architects, Inc.
MCDBA, MCSD
Quote:> Dear All,
> I have a blocking problem on a table when a user
> retrieve all records of the table to a datawindow by
> powerbuilder and works on it, the table is being locked.
> Other user can't do anything. How to release the lock of
> the table?