Maximum number of connections

  • Thread starter Thread starter vraj
  • Start date Start date
V

vraj

Guest
Hi,
we use access for localisation in our application. The business object which accessess the access uses DAO connectivity and we often land to
"Too many client tasks" problem.

is it wise to change the DAO to ADO? if so the above problem will go off?
what are the chances that the problem still persists?

is that access has any limits on the number of connections? like 64, 255? or is that ADO/DAO has any limitaions on the number of concurrent connections to access DB?

Pls help, your help will be highly appreciated.

Thanks,
Venkat.
 
If your tables are Access (Jet actually) then the limit is 255 concurrent users.

Is your database split?
Is the front end stored on the users local drive?
 
Does it matter that I use DAO/ADO connection? does it matter that ADO will improve performace than DAO?
 
If your tables are Jet (you never answered this), ADO will not improve performance. DAO is the NATIVE access method for Jet tables. It is optimized for Jet.

Jet manages database activity by creating an .ldb file. It allows a maximum of 255 concurrent connections.
 

Users who are viewing this thread

Back
Top Bottom