Possible problem with how Concurrency is use...

StrataFrame Forum

Back

Possible problem with how Concurrency is use...

Author	Message
Edhy Rijo	E Edhy Rijo posted 15 Years Ago Topic Details Share Topic
E Group: StrataFrame Users Posts: 2.4K, Visits: 23K	I have a based BO in which I have the following properties setup for all my BOs: DeleteConcurrencyType = OptimisticRowVersion UpdateConcurrencyType = OptimisticRowVersion RowVersionOrTimestampColumn = "RowVersionField" I have a couple of BO in which I don't want to use any Concurrency, so I simply setup these properties: DeleteConcurrencyType = Off UpdateConcurrencyType = Off RowVersionOrTimestampColumn = "RowVersionField" (this was left in, since it should have not effect) Problem: When trying to update a record I get the following exception: The formal parameter "@RowVersionField" was not declared as an OUTPUT parameter, but the actual parameter passed in requested output So it looks like that by leaving the value in RowVersionOrTimestampColumn, will still be used even if the xxConcurrencyType properties are set to OFF, shouldn't this value be ignored when concurrency is OFF? Edhy Rijo
	Reply Like 0
Trent Taylor	Trent Taylor posted 15 Years Ago Post Details Share Post
Group: StrataFrame Developers Posts: 6.6K, Visits: 6.9K	Well, I can look. But I know that if you remove it it won't be used...easy workaround I will add this to a list and look at it when I get a chance.
	Reply Like 0
Edhy Rijo	E Edhy Rijo posted 15 Years Ago Post Details Share Post
E Group: StrataFrame Users Posts: 2.4K, Visits: 23K	Trent L. Taylor (06/24/2009) Well, I can look. But I know that if you remove it it won't be used...easy workaround Sure, it took me some time to track this down. I will add this to a list and look at it when I get a chance. Thanks Edhy Rijo
	Reply Like 0