Good evening folks:
I'm maintaining an Access ADP project that interfaces with a MS SQL Server 2000. I've been noticing looking at the sysprocesses table that for every user in the ADP access creates three processes no matter what the user is doing. Those three processes tend to expand depending on the number of operations being performed by the user.
My question is, letting Access manage the server connections appears to let access create multiple connections to the database. I'm curious if there's a way to force Access (again, having the ADP manage the connection automatically) to use as few connections as possible, or release connections / processes not in use.
I'm maintaining an Access ADP project that interfaces with a MS SQL Server 2000. I've been noticing looking at the sysprocesses table that for every user in the ADP access creates three processes no matter what the user is doing. Those three processes tend to expand depending on the number of operations being performed by the user.
My question is, letting Access manage the server connections appears to let access create multiple connections to the database. I'm curious if there's a way to force Access (again, having the ADP manage the connection automatically) to use as few connections as possible, or release connections / processes not in use.
Comment