>Dan,
>
>SET ANSI_NULL is for the current session. To set ANSI NULL option for DB use sp_dboption system stored procedure.

Thanks for the quick response Sergey!

That worked. Sort of, DATABASEPROPERTYEX([database],'IsAnsiNullsEnabled') now returns 1, but the Merge Agent still returns an error that "SET options have incorrect settings 'ANSI_NULL'" I think this must mean that the agent is still connecting to the subscriber with ANSI_NULL OFF.

Well, the next thing I can try is re-creating the publication, but that will have to wait for the weekend.

>
>>
>>I have a server which I can't change it's ANSI_NULL setting to ON. I've adjust the server default, the database's default, confimed that ANSI NULLS is on for Query Analyzer's connection, SET ANSI_NULLS ON in Query Analyzer (Returned success), but DATABASEPROPERTYEX([database],'IsAnsiNullsEnabled') keeps returning 0. Do I need to restart the server or something?
>>
>>The problem is that I need to coordinate this ANSI_NULL change to two servers involved in merge replication. Replication is failing because I added a computed column, asjusted the publishers ANSI_NULL setting, but the subscriber's ANSI_NULL is OFF. I have not found any way to adjust the connection settings for the Merge Agent, so I assume it uses the defaults? But even if I could specify the setting, doing so in Query Analyzer seems to have no effect.
>>