Hi Peter,

Below is a section on connection pooling that might be of value to you.  It
indicates ways in which you can customize connection pooling using the
connection object.  Try to set some of the parameters and let me know what
happens.

I'm a little concerned, though, about what you said - I'm wondering why your
users are encountering timeout problems and if this is really the result of
sleeping connections - let me know what you discover in this regard.

Bernie
--------------------------
Controlling Connection Pooling with Connection String Keywords
The ConnectionString property of the SqlConnection object supports
connection string key/value pairs that can be used to adjust the behavior of
the connection pooling logic.

The following table describes the ConnectionString values you can use to
adjust connection pooling behavior.

     Name Default Description
     Connection Lifetime 0 When a connection is returned to the pool, its
creation time is compared with the current time, and the connection is
destroyed if that time span (in seconds) exceeds the value specified by
Connection Lifetime. This is useful in clustered configurations to force
load balancing between a running server and a server just brought online.
     A value of zero (0) will cause pooled connections to have the maximum
time-out.

     Connection Reset 'true' Determines whether the database connection is
reset when being removed from the pool. For Microsoft SQL Server version
7.0, setting to false avoids making an additional server round trip when
obtaining a connection, but you must be aware that the connection state,
such as database context, is not being reset.
     Enlist 'true' When true, the pooler automatically enlists the
connection in the current transaction context of the creation thread if a
transaction context exists.
     Max Pool Size 100 The maximum number of connections allowed in the
pool.
     Min Pool Size 0 The minimum number of connections maintained in the
pool.
     Pooling 'true' When true, the connection is drawn from the appropriate
pool, or if necessary, created and added to the appropriate pool.

Hi Peter,

I now see that getting to the viewer's connection object might not be
possible, so my advice doesn't serve any purpose; I will continue to look
into this to see if it's possible.

Bernie

Hi Peter,

OK; I'm at my wits end.  There seems no way of getting at the connection
string of the crystal viewer, even of the crystal reportdocument.  I'd
recommend you post to microsoft.public.dotnet.framework.adonet.  There are
very strong people there who might be able to help us.  If you come up with
anything, please let me know, as I am concerned about this issue for the
same reasons you are.

Bernie

Hi Peter,

Making a little - very little - progress.

1.  I have a message into Crystal re the problem;
2.  I notice that you can change the timeout property in the connection
itself inside crystal reports.  While I see no way there to edit the
connection string itself re pooling, this may help.  For example, it
defaults to 15; I was able to change it to 1250 (presumably seconds) which
may resolve the timeout issues you've encountered.

Yes, it's a pain to have to change all of the reports' connection
properties, but if that's what we down to, at least it may be a solution.
Let me know what you think.

Bernie