Lines Matching refs:p
97 <p>This interface does not really provide an own functionality, it is only for easier
98 runtime identification of report components.</p>
100 <p>A report fulfills several tasks, like storing the structure of its
102 event environment for its contained elements.</p>
140 <p>A spreadsheet document contains 2 families of styles:
141 "PageStyles" and "CellStyles".</p>
148 <p>
152 </p>
214 <p>In case of a <member>CommandType</member> of <member>CommandType::COMMAND</member>,
222 which are not standard SQL, to your database.</p>
231 … <p><member>Command</member> needs to be interpreted depending on the value of this property.</p>
233 <p>This property is only meaningful together with the <member>Command</member>
234 property, thus either <em>both</em> or <em>none</em> of them are present.</p>
242 … <p>The Filter string has to form a SQL WHERE-clause, <em>without</em> the WHERE-string itself.</p>
244 … <p>If a <member>DataSourceName</member>, <member>Command</member> and <member>CommandType</member>
246 row set are to be additionally filtered, the Filter property can be used.</p>
248 …<p>Note that the Filter property does not make sense if a <member>ResultSet</member> has been spec…
249 in the DataAccessDescriptor.</p>
259 <p>The default value of this property is <TRUE/>. By switching it to <FALSE/>, you can pass
260 backend-specific SQL statements, which are not standard SQL, to your database.</p>
262 <p>This property is usually present together with the <member>Command</member> and
264 equals <member>CommandType::COMMAND</member>.</p>