M
Marlon Velasco
Running 2 - Windows 2K SP4 AD domain controllers with dns on each.
Running MS Access 2000 on client pc's.
We have a bunch of access db files connecting to a Pervasive db and
generating reports.
I recently migrated all the data from one server to another including all
the access db files. At first nobody could open the access db files until
the dsn was modified on the client pc's to point to the new server. The
problem now is that although the files open they take about 10 minutes to
open a query (or anything in access). The event log generates event id's
1000 which indicates a dns problem. I have verified that dns is functioning
properly.
I'm not experienced in access or odbc connections.
1. what is the proper procedure for setting up a dsn to the pervasive db?
2. Is a file dsn needed or a system dsn on the client PC's?
3. Is a dsn needed on the server?
4. What do I need to check for the slow response times of access queries?
Any ideas or suggestions would be greatly appreciated.
thanks,
Marlon
Running MS Access 2000 on client pc's.
We have a bunch of access db files connecting to a Pervasive db and
generating reports.
I recently migrated all the data from one server to another including all
the access db files. At first nobody could open the access db files until
the dsn was modified on the client pc's to point to the new server. The
problem now is that although the files open they take about 10 minutes to
open a query (or anything in access). The event log generates event id's
1000 which indicates a dns problem. I have verified that dns is functioning
properly.
I'm not experienced in access or odbc connections.
1. what is the proper procedure for setting up a dsn to the pervasive db?
2. Is a file dsn needed or a system dsn on the client PC's?
3. Is a dsn needed on the server?
4. What do I need to check for the slow response times of access queries?
Any ideas or suggestions would be greatly appreciated.
thanks,
Marlon