Hi Patrick,
Thanks for letting us know about this problem.
Timestamps are numbers that behave in a special way: They can be updated
automatically and they are guaranteed to be uniqe across the database, so
in theory they should come from the data base and not be set by the user to
some arbitrary value. Of course, if one tries to protect some users against
accidentally doing something, one may hurt other users who have a valid
reason to do the same thing...
Where do your timestamps come from? Maybe you could call your SP from
another SP that reads these timestamps so you do not have to set them
manually?
Hartmut Maennel, C# Team (Debugger)
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
>From: "Patrick Seurre" <anonymous@discussions.microsoft.com>
>Subject: SQL timestamp parameters in VS.NET
[quoted text clipped - 11 lines]
>copying and pasting the value from the database - and
>nothing is accepted as valid.