Vague description of login problem 1

[petermeachem]

The application uses Access 97 front end on win98/win95. the data is on sql 7 on nt4.

i'm sorry if this is a bit vague, but I'm 300 miles away and have been getting very vague error descriptions.

On the win 98 pc'c, when a linked table is opened on Access 97/win 98, the user gets a sql login. If they make the user name 'sa', then all is well after that.
On the win95 pc's, they get the same login, but cannot connect.

The programme works fine here, with either sql 7 on sbs 4.5 and the client access 97 on nt4 workstation or win95, or with sql 6.5 on nt4 workstation. it's just at the customer that it doesn't work.

The hardware people said 'named pipes doesn't work, you must use tcp'. That can't be right surely?

Could some kind soul please point me in the right direction?

The connect string used is:-
ConnectString=ODBC;DRIVER=SQL Server;UID=sa;PWD=;DATABASE=CorbyChilled;SERVER=PENT1;Trusted_Connection=Yes; Peter Meachem
peter@accuflight.com

 

[tlbroadbent]

In order to use the Trusted_Connection, sa must be an NT login as well as SQL login. Set Trusted_Connection=No and the App will use SQL authentication to connect. Terry

http://members.home.net/tlbroadbent/index.htm

 

[petermeachem]

Thanks, I'll see if I can get them to try that tomorrow (middle of the night here). Does that mean it will just connect without the users seeing the login? Peter Meachem
peter@accuflight.com

 

[tlbroadbent]

It certainly should. However, in looking at the connection string, I see that sa has no password. That is poor practice as it leaves the SQL Server open to anyone who has the server address and can get to it, whether inseide or outside of the company. If the sa password is indeed NULL, I recommend an immediate change. Terry

http://members.home.net/tlbroadbent/index.htm

 

[petermeachem]

I'm sure you are correct, however, we have a problem currently with connecting to the thing. I don't understand why the 95 pc's (apparently) behave differently to the win98's. I don't know if the odbc dll's need to be at or above a certain rev level. (like your web site by the way) Peter Meachem
peter@accuflight.com

 

[petermeachem]

I thought you would like to know that I have just returned from the customer. The problem was that SQL Server had not been installed so that it was part of the NT domain. Had to install it and all now ok.

Thanks for your help. Peter Meachem
peter@accuflight.com