It's a bug.
You need to apply a service pack for office.
There is a kb article on
http://msdn.microsoft.com/support but I can't
remember what it was, just saw it last week from another post.
--
Jerry Boone
Analytical Technologies, Inc.
http://www.antech.biz
Secure Hosting and Development Solutions for ASP, ASP.NET, SQL Server, and
Access
"Glenn Davy" <vmstech@tpg.com.au> wrote in message
news:pan.2004.01.19.13.46.32.867514@tpg.com.au...[color=blue]
> Hi
>
> Can any one tell me what is meant if access appends a ";1" to the names of
> stored procedures?
>
> Note, that the ";1" isn't already part of the name of the procedures
> name as they exist in the database served from the MSDE2000 server, nor
> does it become part of the name, but it is how they appear it the access
> container window. Two different machines can browse the same database,
> server from the same machine and each see a different version of the name
> (one with the ;1 suffix and one with out). Of course trying to execute or
> design the procedures fails as MSDE simply reports back that the procedure
> doesn't exist.
>
> Another interesting observation is that the problem is machine specific -
> a machine that adds 'sees' the suffix always sees suffix and a machine
> that doesn't never does - even though (we believe) the software (os,
> access version, msdac version and service pack levels are the same)
>
> Any information about what ;1 means, what could be causing it, or how we
> can stop it would just make my week complete
> Thanks
> Glenn[/color]
