P
Phil
Hello
I have a strange behaviour.
I have a datagrid, with articles that have to be produced today or the
day after. In this program one can see the articles, that have already
been planned (just for control). Now it can be, that the planner has
realised that he planned something wrong for this article. So he has
the possiblity to lock it with a button called "lock", which changes a
status in the Database. When he has changed his plan, he can klick
again on the button, which now has the value "unlock". This works
well.
The problem is, that this ASP.NET programm is used by more then one
planner. When an other planer also klicks on the same "lock"-Button
(because he hasn't refreshed the page and can't see that the button
now has the value "unlock") nothing should happen, because it is
already locked. But the strange thing is, that the value sent back of
this button is now not "lock", but "unlock"?! Somehow Microsoft is
trying to be more intelligent, that is ought to be. Because it should
send back "lock", but somehow the program realises, that on the other
computer the Status of the button has changed to "unlock". How can
this happen and how can I prevent this?
BTW I don't use any sessions. So that shouldn't be the problem.
Thanks
Phil
I have a strange behaviour.
I have a datagrid, with articles that have to be produced today or the
day after. In this program one can see the articles, that have already
been planned (just for control). Now it can be, that the planner has
realised that he planned something wrong for this article. So he has
the possiblity to lock it with a button called "lock", which changes a
status in the Database. When he has changed his plan, he can klick
again on the button, which now has the value "unlock". This works
well.
The problem is, that this ASP.NET programm is used by more then one
planner. When an other planer also klicks on the same "lock"-Button
(because he hasn't refreshed the page and can't see that the button
now has the value "unlock") nothing should happen, because it is
already locked. But the strange thing is, that the value sent back of
this button is now not "lock", but "unlock"?! Somehow Microsoft is
trying to be more intelligent, that is ought to be. Because it should
send back "lock", but somehow the program realises, that on the other
computer the Status of the button has changed to "unlock". How can
this happen and how can I prevent this?
BTW I don't use any sessions. So that shouldn't be the problem.
Thanks
Phil