W
Wayne H.
I have a SQL 7.0 database that I have been using as a
backend data store and using Access 2000 .adp as the
frontend. I have also created many stored procedures in
the SQL 7.0 database. The last couple of days I moved
everything from the SQL 7.0 database to another machine
running SQL 2000. I then went into the .ADP and changed
the connection to the new server. The Access 2000 .adp
connected OK to the server, however all the stored
procedures now have a ';1' appended to the end of the
name. And the system stored procedures are also visible.
Needless to say the stored procedures will not run and
they cannot be renamed, opened or edited. I upgraded one
user machine to Access 2003 and everything worked OK. Is
there a patch or setting that I need to change either in
Access 2000 or on the SQL Server 2000? Thanks for your
help
backend data store and using Access 2000 .adp as the
frontend. I have also created many stored procedures in
the SQL 7.0 database. The last couple of days I moved
everything from the SQL 7.0 database to another machine
running SQL 2000. I then went into the .ADP and changed
the connection to the new server. The Access 2000 .adp
connected OK to the server, however all the stored
procedures now have a ';1' appended to the end of the
name. And the system stored procedures are also visible.
Needless to say the stored procedures will not run and
they cannot be renamed, opened or edited. I upgraded one
user machine to Access 2003 and everything worked OK. Is
there a patch or setting that I need to change either in
Access 2000 or on the SQL Server 2000? Thanks for your
help