Script works in DTS, but has problems as a Stored Procedure

[Roobmeister]

I have a script that builds multiple tables and then builds tables from those tables, etc..

Usually, I run the script as a DTS package, and it doesn't have any problems. However, when I save the script as a stored procedure, I think it is compiling the table builds into a different sequence.

As a result, some of the tables are blank when this script is run as a stored procedure.

Do I need to use transactions to prevent this compilation problem, or is there an easier setting that I can use to keep everything in the original sequence?

Thanks in advance.

[Roobmeister]

Anyone have any ideas on this? I can't use "GO", but I am still still having this compilation issue.