RE: ADO.NET Locking SQL Rows On Select Statement
From: Kevin Yu [MSFT] (v-kevy_at_online.microsoft.com)
Date: 07/19/04
- Next message: Kevin Yu [MSFT]: "RE: Repost Can't populate 2nd listbox from selected value of firs"
- Previous message: Kevin Yu [MSFT]: "Re: Can you avoid pulling the primary key ID and tstamp with a bound datagrid"
- In reply to: el_sid: "RE: ADO.NET Locking SQL Rows On Select Statement"
- Next in thread: el_sid: "RE: ADO.NET Locking SQL Rows On Select Statement"
- Reply: el_sid: "RE: ADO.NET Locking SQL Rows On Select Statement"
- Reply: el_sid: "RE: ADO.NET Locking SQL Rows On Select Statement"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 19 Jul 2004 09:50:58 GMT
Hi el_sid,
I don't think it has anything to do with the internals of ADO .NET when
querying views in SQL Server 2000. Could you try to create another view
which does a single select, like "SELECT * FROM asset" and opens the
DataReader from this view? You can also try to open table by selecting from
table directly.
Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."
- Next message: Kevin Yu [MSFT]: "RE: Repost Can't populate 2nd listbox from selected value of firs"
- Previous message: Kevin Yu [MSFT]: "Re: Can you avoid pulling the primary key ID and tstamp with a bound datagrid"
- In reply to: el_sid: "RE: ADO.NET Locking SQL Rows On Select Statement"
- Next in thread: el_sid: "RE: ADO.NET Locking SQL Rows On Select Statement"
- Reply: el_sid: "RE: ADO.NET Locking SQL Rows On Select Statement"
- Reply: el_sid: "RE: ADO.NET Locking SQL Rows On Select Statement"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|