>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 found this sample I was looking for

http://social.msdn.microsoft.com/Forums/en-US/visualfoxprogeneral/thread/2eeed0dc-9199-48cb-910c-c661e9096cfe

Try to apply your NULL settings using the suggestions from this thread.