Arithabort side affects

i recently needed to add an index to a computed column. I know its risky and that the side affects can be quite a pain (the cursorlocation on an adodb recordset setting caught me out for a start!) but i am struggling with scheduled jobs.
Stored procedures that are called from my applications have either been altered to have the required quoted_identifier and/or arithabort settings changed to comply with the new index, or tha app itself calls the set statement on the connection object just prior to the call to the sproc and this seems to work OK, but any sheduled job that references the table will not execute, even a one line exec sproc statement will not execute. It happily runs in QA, but never runs as part of a job because of the arithabort settings. I've tried changing them in the sproc, deleting and re-creating the sproc, i've added them as statements as part of the job step just before the call to the sproc and nothing lets the job execute. What do I do now as i need these jobs to run and i do not want to havre to remove the index.

DaveAlter database test
set arithabort on

This works, ie the scheduled jobs will now run. Can i expect anything untoward to jump out of the closet now with this change at the database level?

Dave