StrataFrame Forum » StrataFrame Application Framework - V1 » Business Objects and Data Access (How do I?) » Possible problem with how Concurrency is use...

Possible problem with how Concurrency is use...

Edhy Rijo — Wed, 24 Jun 2009 07:52:59 GMT

I have a based BO in which I have the following properties setup for all my BOs:
[codesnippet]DeleteConcurrencyType = OptimisticRowVersion
UpdateConcurrencyType = OptimisticRowVersion
RowVersionOrTimestampColumn = "RowVersionField"
[/codesnippet]

I have a couple of BO in which I don't want to use any Concurrency, so I simply setup these properties:
[codesnippet]DeleteConcurrencyType = Off
UpdateConcurrencyType = Off
RowVersionOrTimestampColumn = "RowVersionField" (this was left in, since it should have not effect)
[/codesnippet]

Problem: When trying to update a record I get the following exception:
[quote]The formal parameter "@RowVersionField" was not declared as an OUTPUT parameter, but the actual parameter passed in requested output[/quote]

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?

RE: Possible problem with how Concurrency is use...

Edhy Rijo — Wed, 24 Jun 2009 07:52:59 GMT

[quote][b]Trent L. Taylor (06/24/2009)[/b][hr]Well, I can look. But I know that if you remove it it won't be used...easy workaround :D[/quote]
Sure, it took me some time to track this down. :D

[quote]I will add this to a list and look at it when I get a chance.[/quote]
Thanks :hehe:

RE: Possible problem with how Concurrency is use...

Trent L. Taylor — Wed, 24 Jun 2009 07:27:44 GMT

Well, I can look. But I know that if you remove it it won't be used...easy workaround :D

I will add this to a list and look at it when I get a chance.