Posted by mike on 10/18/07 17:53

The company I work for was recently purchased by another company and I
am tasked with getting out old Access 97 Apps with a SQL back end
working on the new computers they are providing us. These new
computers are part of their Active Directory. The SQL Server is still
part of our old domain. This old domain is going to be hanging around
for a while so I need to be able to get the Access 97 apps on the
clients of the new domain to talk to the SQL Server of the old domain.

We cant set up a trust relationship with the new domain, nor can we
move the SQL Server to the new domain for technical and security
reasons. So...

Before the purchase the System DSN was configured to connect them to
the SQL Server using their domain credentials. They have a local
username in the access app that they logged into the app with, but it
used their domain credentials to connect them to the SQL Server.

When we tried to run the app as it was previously configured, it would
pop an error about SSPI contexts. I did some digging on that and found
out that you can change the protocol order to be named pipes first,
then TCP/IP and it will resolve that error.

We did that and the error did go away. I did have to create a local
user on the SQL server that matched the username they used in the SQL
app. But after I did that, when we run the app we get random
connections to the SQL Server failing. There are some data grids that
do not load any data occasionally. If you back up a bit and go back
in, sometimes it will pull the data, sometimes it wont. Sometimes it
will pop an error about the ODBC connection failing.

Anyone else deal with this before? Any tips?

Thanks,
--Mike

[Back to original message]