i believe that the # is related to creating a group of stored procs that you
can drop with one drop proc stateement.
IE, i think that you can create a proc using TSQL
CREATE PROC PROCNAME, 1
CREATE PROC PROCNAME, 2
or something like that
and then if you just did the DDL DROP PROC PROCNAME it would drop both
PROCNAME;1 and PROCNAME;2
a year ago, I would have diagnosed it as a problem with NT permissions or
ownership
i dont know exactly what causes it-- do your client machines have a common
MDAC level and OS?
do they all use NT authentication or is it SQL Server authentication
if i had to be honest, i thik that the first place i saw this was a novell
environ--- do you have novell?