appended with a semicolon

[Zeph Grenier]

This issue has been reproduced on three different machines running xp pro
xp2 with three different sqlexpress 2005 servers.
The is an mdf db that was upsized from msaccess2000 .mdb to sql 7.0 mdf and
ldf
From sql 7 it was moved to sqlexpress 2005.
Now using a access2000 adp front end, the procedures in the objects list
shows
system objects appended with a semicolon and a paren a 0 and a close paren
as:
;(0)
Other procedure objects are appended with ;1. System objects are now visible
in the objects list, which is not ordinary behavior in Access. Try to make a
new procedure and one gets: Can't find the object StoredProcedure1. Access
is trying to open and create 'storedProcedure1' but the apparent path is
used is sp_storedprocedures;1(sys) which does not exist, but
sp_storedprocedures does exist. Tables and Views behave as usual; only
procedures.
This behavior is only with Access2000, does not happen with Access 2003 or
07 connected to same mdf and ldf files and the same adp file. Office updates
appear to have no influence. I suppose the problem would go away by
scripting the db to sql and recreating, but I would like to have an idea
what is the cause.

 

[Robert Morley]

Upgrade to the latest service pack of Office 2000 and the problem will go away.


Rob

 

[Sylvain Lafontaine]

It's because you didn't apply the latest service pack(s) on the machines
with A2000. To my (limited) knowledge, Office updates won't apply the
latest SP to this older version, only the security hot fixes.

Also, don't use the prefix sp_ for your own stored procedures. It has a
special meaning for SQL-Server and will give you a little less of a
performance (not serious) but could also give you some very hard to find
bugs under some circumstances (much more serious).

 

[boystart]

dfsgsfdgdfgdfg