Hi Mike,

Maybe it's a local setting. I use SQL 7 regularly (I think we're up to sp3), and I cannot create Stored Procs that reference a field or table that do not exist yet. When I attempt to save the new procedure it throws an error and won't let me save. I didn't realize that I might have an option somewhere to stop this behavior.

Guy

>SQL Server 7.0 threw and error? I'm surprised. SQL Server 7.0 and 2000 now do "delayed name resolution." Any objects that a proc depends on are not checked for until the proc is run for the first time.
>
>-Mike