Hi!

These settings should be set for the user logon session, not for the stored procedure. We met the same problem and found no proper solution for it. Just make a recommendation for the users of that stored procedure to call it using following syntax:

SET ANSI_NULLS ON
SET ANSI_WARNINGS ON
exec spMySP

Most all systems that can use SQL Server send commands to SQL Server as a batches, so you can send these lines as a single string in the call to SQL Server.

>Thank's Michael,
>
>I was tried to do so, but it still gives me the same error.
>May be I don't know how to do it, but what I did is righr click on server name, property, connection and then checked warnings and nuls. It still does give me the same error message.