G
Glen Wilkin via DotNetMonster.com
I have a ASP.net applcation, written in C#, that is producing some very
strange behaviour.
Information is stored in a SQL Server 2000 database. The page that records
and stores information to the database functions correctly if only one user
is using the application. However, if there is more than one user the
system seems to get confused.
The stored procedure that saves the new items returns the ID of the new
item, via @@IDENTITY, this is then used by the page to populate itself from
the database. If two people are using the system the one who submits his
data second gets the first persons id back and his page populates with the
other persons data. The system functions correctly for the first person.
I simply do not understand how the @@IDENTITY value can be passed from one
SQL Server session to an ASP.net session that did not create it.
I've removed all session variables and record the @@IDENTITY value in a
hidden field on the page.
Anyone have any suggestions?
Thanks
strange behaviour.
Information is stored in a SQL Server 2000 database. The page that records
and stores information to the database functions correctly if only one user
is using the application. However, if there is more than one user the
system seems to get confused.
The stored procedure that saves the new items returns the ID of the new
item, via @@IDENTITY, this is then used by the page to populate itself from
the database. If two people are using the system the one who submits his
data second gets the first persons id back and his page populates with the
other persons data. The system functions correctly for the first person.
I simply do not understand how the @@IDENTITY value can be passed from one
SQL Server session to an ASP.net session that did not create it.
I've removed all session variables and record the @@IDENTITY value in a
hidden field on the page.
Anyone have any suggestions?
Thanks