Hi
I have a C# app that uses a dataadapter to update a table in a teradata
datawarhouse. It performs an update using a teradata stored procedure. In
teradata, stored procs dont actually return the number of rows updated but
instead return a 0 if successful. This results in a concurrency exception
being raised when the update is performed. Is there anyway to get around this
issue.

Regards
Syed

I have managed to get it to work. i used an output parameter in teradata
which results in the row count set to 1 and thus doesnot cause a concurrency
exception.

"Ali" wrote:

> Hi
> I have a C# app that uses a dataadapter to update a table in a teradata
> datawarhouse. It performs an update using a teradata stored procedure. In
> teradata, stored procs dont actually return the number of rows updated but
> instead return a 0 if successful. This results in a concurrency exception
> being raised when the update is performed. Is there anyway to get around this
> issue.
>
> Regards
> Syed

Ditto .. I was gonna suggest that very approach.


--

- Sahil Malik [MVP]
ADO.NET 2.0 book -
http://codebetter.com/blogs/sahil.ma.../13/63199.aspx
-------------------------------------------------------------------------------------------

"Ali" <(E-Mail Removed)> wrote in message
news:66A0E915-9802-4679-AA47-(E-Mail Removed)...
>I have managed to get it to work. i used an output parameter in teradata
> which results in the row count set to 1 and thus doesnot cause a
> concurrency
> exception.
>
> "Ali" wrote:
>
>> Hi
>> I have a C# app that uses a dataadapter to update a table in a teradata
>> datawarhouse. It performs an update using a teradata stored procedure. In
>> teradata, stored procs dont actually return the number of rows updated
>> but
>> instead return a 0 if successful. This results in a concurrency exception
>> being raised when the update is performed. Is there anyway to get around
>> this
>> issue.
>>
>> Regards
>> Syed