stored procedure;1

[warway]

Can anyone tell me what ;1 means after a stored procedure name. It is only
visible from some PCs in our network And they cannot run the stored
procedures

TIA
Warway

 

[J. M. De Moor]

Remove the ;1 and your procedure will run OK. I have never figured this one
out...but ever since MS SQL 7.0, the ;1 does not work.

Joe

 

[Guest]

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?

 

[Vadim Rapp]

Hello warway:
You wrote in conference microsoft.public.access.adp.sqlserver on Mon, 1 Mar
2004 18:11:29 -0000:

w> Can anyone tell me what ;1 means after a stored procedure name. It is
w> only visible from some PCs in our network And they cannot run the stored
w> procedures

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_aa-az_72sl.asp

Vadim

 

[Brian M. Sockey]

This might be the cause of your problem:

http://support.microsoft.com/default.aspx?scid=kb;en-us;266277

Brian M. Sockey
www.farsightsolutions.com

 

[Dave Smith]

Thanks Brian for the hint.

I copied my C:\Program Files\Common Files\Microsoft
Shared\MSDesigners98 folder and its contents to the
affected computer and it fixed it instantly.

Sincerely,
Dave Smith