Lines Matching refs:p
57 <p>There are various cases where the wizard needs to interact with the user (except of
70 </ul></p>
72 <p>When you do not specify an interaction handler by using the
78 an interaction handler, a newly-created instance of an interaction handler is used.</p>
80 <p>There's one exception to the above, however: Upon creating the copy table wizard,
85 handler, the processing described above, to find another handler, is applied.</p>
104 <p>At creation time, an attempt will be made to obtain the connections described
106 exception.</p>
108 <p>If the connection has been newly created by the wizard (e.g. because the
110 then this connection will be disposed upon disposal of the wizard.</p>
116 … <p>The following members of the <code>DataAccessDescriptor</code> are supported, and evaluated
128 are required.</p>
130 … <p>Additionally to the obvious restrictions (such as that creating a view is not possible
144 Violating any of the above restrictions will result in an error at creation time.</p>
150 … <p>Only <code>DataSourceName</code>, <code>DatabaseLocation</code>, <code>ActiveConnection</code>
152 …n the order mentioned here, so if multiple of the are present, only the first one is evaluated.</p>
154 <p>Also, at the moment the connection which is implied by either of the settings above
156 it is not sufficient to pass an SDBC-level connection.</p>
158 <p>Note that creating a view (see <member>CopyTableOperation::CreateAsView</member>) is
159 not supported if the target connection is an SDBC-level connection only.</p>
194 <p>The only difference to the <member>create</member> constructor is that
197 run.</p>
202 <p>When specifying this parameter, you should use an implementation
205 handle all requests described <a href="#interaction">above</a>.</p>