T
techjohnny
Recently we had our server crash and had to be replaced. After
replacing, our Access DB that resided on the original server was moved
to a new server. The Access 97 database is accessible to the Windows
clients on a 2008 File Share.
The biggest problem now is the performance. We scan items into the
database and there seems to be major latency issues. I'm wondering if
maybe some name resolution is failing, and if that is the case, what
tools are available to will help elevate the problem?
Or maybe the database at 275MB is reaching a size that when accessing
over a network is very slow? The database has already been jetcomped
many times, but still very slow.
Regards,
--tj
replacing, our Access DB that resided on the original server was moved
to a new server. The Access 97 database is accessible to the Windows
clients on a 2008 File Share.
The biggest problem now is the performance. We scan items into the
database and there seems to be major latency issues. I'm wondering if
maybe some name resolution is failing, and if that is the case, what
tools are available to will help elevate the problem?
Or maybe the database at 275MB is reaching a size that when accessing
over a network is very slow? The database has already been jetcomped
many times, but still very slow.
Regards,
--tj