You can try to send a SET ARITHABORT ON on the connection that you use to
execute the stored procedure. Alternatively you can make a command object
(type Text) with commandtext like "SET ARITHABORT ON EXEC procedurename
@par1,@par 2 " when you want to execute the stored procedure.
Marc
"Ollie Riches" <(E-Mail Removed)> wrote in message
news:#(E-Mail Removed)...
> it appears that an index is causing this to occur but the database is out
of
> my control is there any other way to resolve this with out removing the
> index?
>
> Cheers
>
> Ollie Riches
>
> "Ollie Riches" <(E-Mail Removed)> wrote in message
> news:O#(E-Mail Removed)...
> > found this....
> >
> > http://www.dotnet247.com/247referenc...37/187707.aspx
> >
> > Ollie Riches
> >
> > "Ollie Riches" <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed)...
> > > I have a stored procedure that is being called from ado.net and it is
> > > failing with an exception that is related to the option ARITHABORT -
> > 'UPDATE
> > > failed because the following SET options have incorrect settings:
> > > 'ARITHABORT'.
> > >
> > > This stored procedure works perfectly fine from query analyzer and
from
> > > enterprise manager in sql server. Is this a problem with ado.net?
> > >
> > > The database is sql server 2000 with .net framework version 1.1
> > >
> > > Cheers in advance
> > >
> > > Ollie Riches
> > >
> > >
> >
> >
>
>