I have a proc that was working fine in ODBC. Now that I've switched to OLE DB it's throwing up an error. If I put "SET ANSI_WARNINGS OFF" inside the proc it works. If I take out that SET statement and instead put ANSINPW=No in the connection string it doesn't work. I had a similar problem with some other procs but they were fixed with ANSINPW=No. Why is this one the exception?