|
|
Posted by mike on 10/24/07 15:01
We have a Access app that has been split with the backend on SQL 2k.
We setup an ODBC connection on the clients to point to the SQL server
and we are using NT Auth to connect to the SQL Server. Its been
working this way for years.
We need to change it up so that the users are not using NT Auth to
connect to the SQL Server and we are running into a problem.
The first couple forms work as they always do, it searchs, pulls
records etc. When we get a little deeper into the Access app there are
some data grids that are loaded with data from the SQL Server. When
these are displayed they are solid white, like they are not getting
any data from the SQL Server. If we close that form and go back into
it, its populated with data. If we close that form, we get an error
about not being able to connect to the ODBC datasource.
Its reproduceable on a consistent basis I just cant figure out why its
doing that. It used to be setup this way (no domain auth) for years
and then we switched to domain auth to make it easier to manage the
users. Now that we are going back to the old way its freaking out.
As a test I built a new XP Pro box that is not part of the domain and
a new SQL 2k box that is not part of the domain and copied the
database to the new SQL box to try a fresh setup with no mods done by
me and its the same thing.
Any ideas?
Navigation:
[Reply to this message]
|