DynamicConnections
------------------
Demonstrates how to set ConnectionString and other Connection properties for a data set at run time. 

Using run-time-only property C1DataSet.DynamicConnections, you can specify 
Connection objects that will substitute schema connections at run time.

By default, if C1DataSet.DynamicConnections is empty, data fetch and
update for this data set uses the connections specified in the schema.
Schema connections can be changed at run time in the CreateSchema event (for
example, to set their ConnectionString at run time) but changes in CreateSchema
event occur only once and affect all data sets attached to that schema.
If you need to change connections at run time on a per-data set basis, or
change them for a single data set more than once, use the
C1DataSet.DynamicConnections property.

Add a connection object for each connection you want to change at run time
for this data set. Usually, you will add a copy of a schema connection object(s)
using Connection.Clone(). Alternatively, you can create new connection objects from
scratch, for example, new C1OleDbConnection(). You are not allowed to add existing
connection objects from schema to DynamicConnections, which prevents you
from unintentionally affecting other data set attached to the same schema.

Set the desired properties of the connection object. Usually, only the
ConnectionString needs to be changed in connection objects obtained with 
Connection.Clone(). If you created a new connection object, without using Clone(),
set its Name property to the name of the schema connection you want to modify.

When the data set performs a fetch or update operation while its DynamicConnections
collection is not empty, it first looks for connection properties in DynamicConnection,
and only then, if not found, in the schema. If DynamicConnections contains a connection
with the same Name as the schema connection, that DynamicConnections element is
used instead of the schema connection.








