KabirPatel
Registered User.
- Local time
- Today, 16:51
- Joined
- Nov 16, 2006
- Messages
- 38
Hi,
I developed an .adp that is being used by 270 people. Each time somebody connects to the database via the application I see 2 or 3 connections for each person.
The .adp has a number of forms that are bound to SQL Server stored procedures.
The application also uses ADO to execute stored procedures for reports.
Each of my events that runs a report uses the following:
dim cmd as new ADODB.Command
set cmd.ActiveConnection = CurrentProject.Connection
If I were to set each connection object once via a class (or module) rather than within each event would this prevent numerous connections taking place for each user?
What other methods are there for reducing the number of connections per user?
Thanks,
Kabir
I developed an .adp that is being used by 270 people. Each time somebody connects to the database via the application I see 2 or 3 connections for each person.
The .adp has a number of forms that are bound to SQL Server stored procedures.
The application also uses ADO to execute stored procedures for reports.
Each of my events that runs a report uses the following:
dim cmd as new ADODB.Command
set cmd.ActiveConnection = CurrentProject.Connection
If I were to set each connection object once via a class (or module) rather than within each event would this prevent numerous connections taking place for each user?
What other methods are there for reducing the number of connections per user?
Thanks,
Kabir
