Thanks a lot Frans,
I really liked your conclusion:
> > - Is it a limitation of SQL Server compared to Oracle?
>
> In a way it is, if you want to use SqlServer as if it is
Oracle.
> However from a logical point of view it isn't really, they just
defined
> 'current version' a little differ
Thanks for responding Richard,
I was in a hurry so as well as posting to this mailing list I kept on
looking for a solution. A person called David Browne finally gave me the
explanation of my problem. It is because of a difference between Oracle
and Sql Server regarding transactions. For those who
Whoops,
I wrote:
> I have a method that explicitly opens a connection and begins a
> transaction on SQL Server 2000. I use the System.Data.SqlClient.
>
> Before commiting (or rollbacking) this transaction I need to open
> another connection to use with a datareader. What is important to note
>
> I have a method that explicitly opens a connection and begins a
> transaction on SQL Server 2000. I use the System.Data.SqlClient.
>
> Before commiting (or rollbacking) this transaction I need to open
> another connection to use with a datareader. What is important to note
> is that I'm not inte
contention.
Regards
Richard Blewett
DevelopMentor
-Original Message-
From: Moderated discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED] On Behalf Of Jérôme Grelier
Sent: 25 March 2003 14:34
To: [EMAIL PROTECTED]
Subject: [ADVANCED-DOTNET] Transactions on SQL Server with ado.net
Hi
Hi,
I have a method that explicitly opens a connection and begins a
transaction on SQL Server 2000. I use the System.Data.SqlClient.
Before commiting (or rollbacking) this transaction I need to open
another connection to use with a datareader. What is important to note
is that I'm not interested
