Access 2000 Developer and SQL Server 7.0

[Michael]

I am using MS Access 2000 on an Windows XP machine and am trying to
use
the Upsizing Tool in Access 2000 to upsize an Access 2000 database to
use with Microsoft SQL Server 7.0.

My MS Access 2000 version is part of an Office 2000 Developer Edition
upgrade from Office 97. Included in the Office 2000 SR-1 Developer
package is a disk entitled Microsoft SQL Server 7.0 that I have
installed.

When I try to upsize a database using the Access 2000 tool a dialog
box comes up including the question "What Server would you like to use
for this database?" In this box "Microsoft SQL Server 7.0" is aleady
there. When I click OK the following error message comes up:
Connection failed:
SQLState '01000'
SQL Server Error: 1231
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen(Connect())
Connection failed:
SQLState '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server
does not exist or access denied.
Can anyone please enlighten me and provide some possible solutions.
Cheers
Michael

[Ted Theodoropoulos]

unfortunately, i can't provide any information on the particular error
you're getting. what i can tell you, however, that the upsizing tool
in A2K is a total piece of shit. i wouldn't waste my time with it if
i were you. most of the decisions the wizard makes are horrendous.
in almost all cases, the best way to upsize the database is to
recreate the access tables and queries manually in SQL. u can cut and
past the sql access uses sometimes but the joins are impossible to
read. there are several situations where the access sql is not
usuable by SQL Server.

mw*****@timaru.com (Michael) wrote in message news:<6d**************************@posting.google. com>...

I am using MS Access 2000 on an Windows XP machine and am trying to
use
the Upsizing Tool in Access 2000 to upsize an Access 2000 database to
use with Microsoft SQL Server 7.0.

My MS Access 2000 version is part of an Office 2000 Developer Edition
upgrade from Office 97. Included in the Office 2000 SR-1 Developer
package is a disk entitled Microsoft SQL Server 7.0 that I have
installed.

When I try to upsize a database using the Access 2000 tool a dialog
box comes up including the question "What Server would you like to use
for this database?" In this box "Microsoft SQL Server 7.0" is aleady
there. When I click OK the following error message comes up:
Connection failed:
SQLState '01000'
SQL Server Error: 1231
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen(Connect())
Connection failed:
SQLState '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server
does not exist or access denied.
Can anyone please enlighten me and provide some possible solutions.
Cheers
Michael

[Josh Armstrong]

From just reading the error, you need to give the dialoge box that is
asking for the server that SQL7 is on you must enter the name of the
server itself. For example one of my SQL boxes is names "Max", when
that box comes up I would enter Max.

mw*****@timaru.com (Michael) wrote in message news:<6d**************************@posting.google. com>...

I am using MS Access 2000 on an Windows XP machine and am trying to
use
the Upsizing Tool in Access 2000 to upsize an Access 2000 database to
use with Microsoft SQL Server 7.0.

My MS Access 2000 version is part of an Office 2000 Developer Edition
upgrade from Office 97. Included in the Office 2000 SR-1 Developer
package is a disk entitled Microsoft SQL Server 7.0 that I have
installed.

When I try to upsize a database using the Access 2000 tool a dialog
box comes up including the question "What Server would you like to use
for this database?" In this box "Microsoft SQL Server 7.0" is aleady
there. When I click OK the following error message comes up:
Connection failed:
SQLState '01000'
SQL Server Error: 1231
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen(Connect())
Connection failed:
SQLState '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server
does not exist or access denied.
Can anyone please enlighten me and provide some possible solutions.
Cheers
Michael

[Ted Theodoropoulos]

that error is a general error that can appear for a multitude of
reasons. the sql server not existing and access being denied are VERY
different situations yet u get the same error. if memory serves u get
that error in the client tools themselves such as QA and EM.

try pinging the box and see if u get a response. if so then make sure
ur sql is running on port 1433. if it isn't (which many servers
aren't after slammer) then you'll need the client network utility to
configure ur client.

jo***********@socal.rr.com (Josh Armstrong) wrote in message news:<b6**************************@posting.google. com>...

From just reading the error, you need to give the dialoge box that is
asking for the server that SQL7 is on you must enter the name of the
server itself. For example one of my SQL boxes is names "Max", when
that box comes up I would enter Max.

mw*****@timaru.com (Michael) wrote in message news:<6d**************************@posting.google. com>...

I am using MS Access 2000 on an Windows XP machine and am trying to
use
the Upsizing Tool in Access 2000 to upsize an Access 2000 database to
use with Microsoft SQL Server 7.0.

My MS Access 2000 version is part of an Office 2000 Developer Edition
upgrade from Office 97. Included in the Office 2000 SR-1 Developer
package is a disk entitled Microsoft SQL Server 7.0 that I have
installed.

When I try to upsize a database using the Access 2000 tool a dialog
box comes up including the question "What Server would you like to use
for this database?" In this box "Microsoft SQL Server 7.0" is aleady
there. When I click OK the following error message comes up:
Connection failed:
SQLState '01000'
SQL Server Error: 1231
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen(Connect())
Connection failed:
SQLState '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server
does not exist or access denied.
Can anyone please enlighten me and provide some possible solutions.
Cheers
Michael