All of a sudden, Stored procedure names are different

  • I have an Access 2000 adp (ade) app that has been running smoothly on Windows 2000 platform with a SQL 2000 backend database. Recently, the app has been installed on an XP Professional desktop and immediately ran into the problem where all the Stored Procedures in the SQL 2000 database are interpreted by Access 2000 connection as having ";1" added to the end of each Stored Procedure name.

    Actual SQL 2000 database has the correct names for the Stored procedures (without ;1 at the end of the names). However, the data source behind the various forms are pointing to the correct names of the stored procedures however the Access project shows these names as having ";1" added to the end of each stored procedure name, therefore creating a discrepancy between the real source and what the project seems to think.

     

    Just to try something new, I created a new Access 2000 project and Connected to the same back-end SQL database. At the end of the connection process only the Stored Procedures name were different, showing ;1 added to the end of each stored procedure's name. Naturally the names are correct (without ;1) when you look at the stored procedures in the enterprise manager.

     

    Any ideas would be greatly appreciated

     

    Thanks

     

  • I'm having the same problem but with Access 2000 (9.0.6926 SP-3) and Windows 2000 Pro (Ver 5.0 Build 2195: SP 4).

    I've got 100 identical machines, all burned from the same image, and one machine thats doing this.

    I cannot find any other references on the net so I guess it's not very common.

    Have you found a soultion yet?

  • Oh bugger, just found another machine that is doing the same thing.

    <good news>When I use the same logon on my test machine everything is fine so it must be the machine.</good news>

     

  • Found through Technet that Office 2000 needs to have SR1/1A upgraded to on the XP professional machines for the reported problem to be resolved. I did that and now the problems went away. I further upgraded to SP-3 and still no problems.

     

    It is interesting that Windows 2000 computers with a version less than SR1/1A has been working just fine.

     

     

  • After you last post I've run the SR1 install on the problem machines and it fixes it. Not sure why these two machines are affected and none of the others, however that gives me an easy fix I can pass on to the Help Desk.

    Thanks for your help.

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply