2 questions:

[Rob]

Hi Everyone,

First, if MSDE 2000 is (local) on trusted NT credentials on my machine, I
can connect to it from Access just fine. But later I may wish to experiment
with TCP/IP and/or Named Pipes. To that eventual end, there is something
I'm noticing when my Access 2000 launches: it's trying to go to Destination
IP: 255.255.255.255, Port 1434.

I have MSDE 2000 on 192.168.0.1, Port 1433 on a local loopback. Is this the
reason why Access keeps throwing variations on this pie in my face:

[Pipes or TCP/IP Sockets]SQL Server does not exist or access denied.
[Pipes or TCP/IP Sockets]ConnectionOpen (Connect()).

My second question is: Where--in which directory--is NorthwindCS.sql
supposed to reside in order to get recognized by NorthwindCS.adp?

(I've never done this Access to SQL Server stuff before.) Thank you for any
assistance that you can provide.

 

[BJ Freeman]

1) make sure, using the sql network utility that you have TCP/ip active on
the MSDE and where the ADP is.
2) you can connect because you are using pipe which uses NT authorization.
3) TCPIP only uses SQL userID'
4) you can play with multimode, but I don't recommend designing around it.
5) in your ADP when you are using TCPIP use the IP addressees as the server
name.
6) make sure any firewall allow both port 1434 and 1433.
7) I believe MSDE 2K uses one other port.
8) 255.255.255.255 is a broadcast to find any thing listening on port 1434.
sort of like an autofind.
9) *.sql are only use to make a DB in the sQL server. after that, they
server no function.
10) open the query analyzer and load the SQL file. I am not sure if it has a
make DB command in it.
11) if not create the DB then use the Drop down in the query analyzer to
select the DB you want to run the sQL script against.

Welcome to many winter hours of enjoyment as you trek up the SQL server
learning curve.

 

[Rob]

BJ, thanks.

I have a few more questions to ask about MSDE when I get chance.

-Rob

---

1) make sure, using the sql network utility that you have TCP/ip active on
the MSDE and where the ADP is.
2) you can connect because you are using pipe which uses NT authorization.
3) TCPIP only uses SQL userID'
4) you can play with multimode, but I don't recommend designing around it.
5) in your ADP when you are using TCPIP use the IP addressees as the server
name.
6) make sure any firewall allow both port 1434 and 1433.
7) I believe MSDE 2K uses one other port.
8) 255.255.255.255 is a broadcast to find any thing listening on port 1434.
sort of like an autofind.
9) *.sql are only use to make a DB in the sQL server. after that, they
server no function.
10) open the query analyzer and load the SQL file. I am not sure if it has a
make DB command in it.
11) if not create the DB then use the Drop down in the query analyzer to
select the DB you want to run the sQL script against.

Welcome to many winter hours of enjoyment as you trek up the SQL server
learning curve.

Hi Everyone,

First, if MSDE 2000 is (local) on trusted NT credentials on my machine, I
can connect to it from Access just fine. But later I may wish to experiment
with TCP/IP and/or Named Pipes. To that eventual end, there is something
I'm noticing when my Access 2000 launches: it's trying to go to Destination
IP: 255.255.255.255, Port 1434.

I have MSDE 2000 on 192.168.0.1, Port 1433 on a local loopback. Is this the
reason why Access keeps throwing variations on this pie in my face:

[Pipes or TCP/IP Sockets]SQL Server does not exist or access denied.
[Pipes or TCP/IP Sockets]ConnectionOpen (Connect()).

My second question is: Where--in which directory--is NorthwindCS.sql
supposed to reside in order to get recognized by NorthwindCS.adp?

(I've never done this Access to SQL Server stuff before.) Thank you for any
assistance that you can provide.