>Well, it appears a SP like this will work.

>procedure ExecuteSQL(SQLstatement)
>set null off
>execscript(SQLStatement)

>Now the question is what kind of security holes does this create? Any thoughts? If I knew how to set null off by default maybe I wouldn't need the SP.

I have to read up on such things myself - I'd start with the connectionstirng.

HTH

thomas