Re: adLockReadOnly problem with SQL Server 2000
From: Stephen Howe (stephenPOINThoweATtns-globalPOINTcom)
Date: 03/08/05
- Previous message: Jan Hyde: "Re: adLockReadOnly problem with SQL Server 2000"
- In reply to: Jethro: "adLockReadOnly problem with SQL Server 2000"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 8 Mar 2005 12:53:39 -0000
> which runs fine. However, when other users try and update "PropertyImage",
> Enterprise Manager shows that my app is blocking their update. Since my
app
> can take a while to run, it times them out.
>
> Shouldn't the lock type be "read only" by default, so no blocking can
occur.
It is readonly by default and the chances are it is readonly.
But even readonly does not mean it will not block others.
> Is there any sense in disconnecting the recordset to avoid blocking other
> users. I never need to update the date, just read it
You won't be able to disconnect the recordset.
You have made a server-sided, forward only cursor.
I imagine that this blocks the updates by others of these tables as the
server is _still_ delivering the data.
Switch to a client-sided cursor.
You can disconnect then.
I would suggest reading up on cursortypes
Stephen Howe
- Previous message: Jan Hyde: "Re: adLockReadOnly problem with SQL Server 2000"
- In reply to: Jethro: "adLockReadOnly problem with SQL Server 2000"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|