The dateformat string solution, are there other ways to deal witht that (other than telling it to NEVER participate in optimistic concurrency)?
I mean to say, how can that be displayed to the user in a way that is less "awful" for them to look at?
Could it be tied into some sort of date/time picker control so the user never has to see that?
EDIT: What if a datetime stamp was used (added as a whole new field) could optimistic concurrency use that field and then all the other fields would be set to NEVER participate so you'd have the best of both worlds?
Maxer_Ars
Member
76 Points
183 Posts
Re: AdventureWorks Database - error updating an existing row.
Apr 04, 2008 04:35 PM|LINK
The dateformat string solution, are there other ways to deal witht that (other than telling it to NEVER participate in optimistic concurrency)?
I mean to say, how can that be displayed to the user in a way that is less "awful" for them to look at?
Could it be tied into some sort of date/time picker control so the user never has to see that?
EDIT: What if a datetime stamp was used (added as a whole new field) could optimistic concurrency use that field and then all the other fields would be set to NEVER participate so you'd have the best of both worlds?