JOhn:
>>Then you'd need to write and maintain dozens or hundreds of lines of SP code >>to manage the partial parameter list. All this for "easier" maintenance >>and/or performance.
No way. All ya gotta do is initialize the SQL Server SP parms to null, then they won't balk at an empty value.
>>That's my point. As a busy theatre surgeon I don't want to know about it. I >>want to enter whatever part interests me and have it just save without being >>asked whether to overwrite what the anaesthetist or nurse entered into >>different fields at the same time. With RVs, that is all there with no extra >>effort.
I thought you were asking me how my data classes handle a write after write update conflict? If my customer didn't want it, I'd remove it.
Regards
Charlie
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only