The problem is that on the ADO Connection object, I see no native property for this and the Properties collection cannot be accessed before the connection is made, not that it matters because I don't see one there, either. And even if it could, it would probably be read-only.


>It doesn't make any difference.
>
>>Sorry - I left out that this was a DSN-less connection.
>>
>>>AFAIK, you can specify them in the connection properties before connecting but not in the connection string.
>>>
>>>>Is there a parameter I can include in an OLEDB connection string to the following set commands OFF, so I can avoid setting them off in the stored proc(s) that need them off?
>>>>
>>>>ANSI_WARNINGS
>>>>ANSI_NULLS
>>>>CONCAT_NULL_YIELDS_NULL
>>>>
>>>>I've already tried
>>>>
>>>>

>>>>AnsiNPW=no        -- works in ODBC
>>>>Ansi warnings=off -- puts into Extended properties attribute and adds
>>>>                     several other parameters as well, but no effect
>>>>

>>>>Well, I say no effect - in SQL Profile, the Audit Login for connections show that warnings are on, and there is no batch after (like from a VFP SPT connection) that then sets them off, nor does it show if this is an existing connection.
>>>>
>>>>TIA