For a client utility I have written for another one of my apps. I am
using ADO to connect to an Access DB. Normally I use Titan Access 2000
controls, but I needed to use ADO because it has the "Sort" property
where you tell it to sort the data by a field name.
This is fine, but what I have confused myself about now is, the user will
have the client util running most of the time.
I am concious of the fact that the ado needs a connection to the Access
DB, and this potentually is connected all the time, but since teh app. is
MDI, when a form is opened, it will then create a connection to the db,
and close it when the form is closed.
BUT if the form is NOT closed, the connection still exists.
What I would like if any on can, is confirmation of the fact that if say
100 people have a connection to the access db, but its not actually in
use, its still ok. Obviously if 100 people are hitting the DB then there
is a problem.
Or to put it another way, a 100 connections is fine, but 100 connections
being used at the same time is a problem.
I hope people understand what I am meaning.
Jeremy
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
To UnSub, send email to: [EMAIL PROTECTED]
with body of "unsubscribe delphi"
Web Archive at: http://www.mail-archive.com/delphi%40delphi.org.nz/
