My machine has been upgraded from the SQL 7 client to the SQL 2000 client. It is running under NT4 sp6 but I have another machine running Win2000 that has the same problems.
I am linking to my SQL database using Access 2000 as the front end, a machine DSN and Microsoft SQL Server ODBC Driver Version 03.80.0194.
The DSN has been set up to use SQL Server authentication.
What used to happen is that as soon as I tried to open a table in the database through a link a login box popped up and I logged in.
What now happens is that I get an error message saying that I cannot be connected using NT authentication. I then have to clear a tick box that opts for NT authentication and this allows me to use SQL server authntication. I then have to change my login name from my NT login name to my SQL login name and finally I get to enter a password and get in.
Next time I open Access I have to go through the whole process again.
Why has my machine lost the ability to remember that I use SQL logins and to remember my SQL login name from one session to the next? The DSN clearly opts for SQL server authntication.
For what it's worth Query Analyzer can remember from one session to the next my login method. However, a similar problem arises if I try to refresh an Excel pivot table which is poined at the server.
As a developer I can just cope with this, although with a little irritation. However, I have end users who could soon be upgraded and they would be upset to get such error messages.
My gut feeling is that the driver 03.80.0194 is at fault as Access 2000 and Excel were perfectly happy until the SQL client was upgraded.
Ken
I am linking to my SQL database using Access 2000 as the front end, a machine DSN and Microsoft SQL Server ODBC Driver Version 03.80.0194.
The DSN has been set up to use SQL Server authentication.
What used to happen is that as soon as I tried to open a table in the database through a link a login box popped up and I logged in.
What now happens is that I get an error message saying that I cannot be connected using NT authentication. I then have to clear a tick box that opts for NT authentication and this allows me to use SQL server authntication. I then have to change my login name from my NT login name to my SQL login name and finally I get to enter a password and get in.
Next time I open Access I have to go through the whole process again.
Why has my machine lost the ability to remember that I use SQL logins and to remember my SQL login name from one session to the next? The DSN clearly opts for SQL server authntication.
For what it's worth Query Analyzer can remember from one session to the next my login method. However, a similar problem arises if I try to refresh an Excel pivot table which is poined at the server.
As a developer I can just cope with this, although with a little irritation. However, I have end users who could soon be upgraded and they would be upset to get such error messages.
My gut feeling is that the driver 03.80.0194 is at fault as Access 2000 and Excel were perfectly happy until the SQL client was upgraded.
Ken