Upgrading to SQL Server 2005 Now Sprocs renamed ...;1

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Lauren Quantrell
    #1

    Upgrading to SQL Server 2005 Now Sprocs renamed ...;1

    I recently upgraded to SQL Server 2005 from SQL Server 2000, and
    Access 2007 from 2003. When I run a ADP created in Access 2000 (which
    worked fine in Access 2002 and 2003) in Access 2007 everything is
    fine, but when I go back and run it in Access 2000, all the sprocs are
    renamed: SprocName;1 (with ";1" added to each sproc name) so they are
    not recognized in Access 2000.
    Is there a workaround to this?
    Thanks,
    lq
    Tags: None
    • lyle fairfield
      #2
      Re: Upgrading to SQL Server 2005 Now Sprocs renamed ...;1

      http://support.microsoft.com/default.aspx?scid=kb;[LN];Q269824

      On Aug 9, 9:23 am, Lauren Quantrell <laurenquantr.. .@hotmail.com>
      wrote:
      I recently upgraded to SQL Server 2005 from SQL Server 2000, and
      Access 2007 from 2003. When I run a ADP created in Access 2000 (which
      worked fine in Access 2002 and 2003) in Access 2007 everything is
      fine, but when I go back and run it in Access 2000, all the sprocs are
      renamed: SprocName;1 (with ";1" added to each sproc name) so they are
      not recognized in Access 2000.
      Is there a workaround to this?
      Thanks,
      lq

        Comment

        • Chris O'C via AccessMonster.com
          #3
          Re: Upgrading to SQL Server 2005 Now Sprocs renamed ...;1

          If your Access 2000 installation is missing SP1, it's missing the two
          subsequent SPs. Make sure those get installed too, or you're going to have
          worse problems.

          Chris
          Microsoft MVP


          Lauren Quantrell wrote:
          >I recently upgraded to SQL Server 2005 from SQL Server 2000, and
          >Access 2007 from 2003. When I run a ADP created in Access 2000 (which
          >worked fine in Access 2002 and 2003) in Access 2007 everything is
          >fine, but when I go back and run it in Access 2000, all the sprocs are
          >renamed: SprocName;1 (with ";1" added to each sproc name) so they are
          >not recognized in Access 2000.
          >Is there a workaround to this?
          --
          Message posted via AccessMonster.c om
          http://www.accessmonster.com/Uwe/Forums.aspx/databases-ms-access/200808/1


            Comment

            • Lauren Quantrell
              #4
              Re: Upgrading to SQL Server 2005 Now Sprocs renamed ...;1

              On Aug 9, 10:04 am, lyle fairfield <lyle.fairfi... @gmail.comwrote :
              http://support.microsoft.com/default.aspx?scid=kb;[LN];Q269824
              >
              On Aug 9, 9:23 am, Lauren Quantrell <laurenquantr.. .@hotmail.com>
              wrote:
              Thanks. This is a new machine with both Access 2007 and 2000 recently
              installed. It's been a long time since I installed a copy of 2K on a
              machine and I had forgotten all the Service Packs. Thanks.
              lq
              >
              >
              >
              I recently upgraded to SQL Server 2005 from SQL Server 2000, and
              Access 2007 from 2003. When I run a ADP created in Access 2000 (which
              worked fine in Access 2002 and 2003) in Access 2007 everything is
              fine, but when I go back and run it in Access 2000, all the sprocs are
              renamed: SprocName;1 (with ";1" added to each sproc name) so they are
              not recognized in Access 2000.
              Is there a workaround to this?
              Thanks,
              lq- Hide quoted text -
              >
              - Show quoted text -

                Comment

                Previous template Next
                Working...