ÿþ<Html> <CET_ADSENSEH> <script type="text/javascript"><!-- google_ad_client = "pub-5291624188982543"; /* 728x90, A>740=> 04.02.08 */ google_ad_slot = "9704471239"; google_ad_width = 728; google_ad_height = 90; //--> </script> <script type="text/javascript" src="http://pagead2.googlesyndication.com/pagead/show_ads.js"> </script> </CET_ADSENSEH> <CET_HEADER> <table width="100%" border="0"> <tr> <td width="220"><a href="http://www.chmlib.com"><img src="http://www.chmlib.com/chmlib_logo.gif" alt="CHMlib Logo" width="220" height="93" border="0"></a></td> <td width="240"><div align="center"><span class="style6"><B><a href="http://www.chmlib.com">Free Online Library Of Help Files</a></B><a href="http://www.chmlib.com"><B>.<br> Read help files in convenient way.</B></a></span></div></td><td ><a href="http://www.projetex.com/">Leading Translation Management System for Translation Agencies</a>, <a href="http://www.to3000.com/">Top Translation Management Software for Freelance Translators</a>, <a href="http://www.exactspent.com/">Time Tracking Software</a>, <a href="http://www.anycount.com/">Word Count, Character Count and Line Count Software</a>, <a href="http://www.catcount.com/">Computer Assisted Translation Tool for Easy Word Count</a>, <a href="http://www.clipcount.com/">Clipboard Character Count Software</a>, <a href="http://www.anymem.com/">User-Friendly Translation Memory Software</a>, <a href="http://www.anylexic.com/">Terminology Management Software</a>, <a href="http://www.anylexic.com/Terminology-Management-Software-Server-Features.html">Terminology Management Server</a>, <a href="http://www.winlexic.com/">Microsoft Glossary Software</a>, <a href="http://www.acrolexic.com/">Dictionary of Acronyms</a>, <a href="http://www.langmates.com/">Social Network for Translators and Translation Agencies</a>, <a href="http://www.acronymia.com/">Acronyms and Abbreviations Search Engine</a>, <a href="http://www.translation3000.com/Translation/Russian_Translation.html">Russian Translation Lab</a>, <a href="http://www.translation3000.com/Translation/Ukrainian_Translation.html">Ukrainian Translation Lab</a>.</td></tr></td> </tr> </table> <table width="100%" border="0"> <tr> <td colspan="2" bgcolor="#0099FF"><div align="right" class="style1"> <div align="center"><font color="#FFFFFF">You are reading help file online using chmlib.com</font></div> </div></td> </tr> </table> </CET_HEADER> <Head></Head><Title>TPSCCustomFltBld</Title><Body><font face="Arial"><font SIZE="2"> <P Align="left"> <font SIZE="3"><B>TPSCCustomFltBld.FilterOptions</B></font><BR> <A href="TPSCCustomFltBld.html">TPSCCustomFltBld</A>&nbsp&nbsp&nbsp&nbsp&nbsp</P>Specifies different customization options.<BR> <BR> <B>property</B> FilterOptions: TPSCFltBldOptions;<BR> <BR> <font SIZE="2"><B>Unit</B></font><BR> <A href="psc_fltbox.html">psc_fltbox</A><BR> <BR> <font SIZE="2"><B>Description</B></font><BR> Use FilterOptions to get or set different customization options that affect Filter/SQL generation and other aspects of the component behavior. FilterOptions is a set property and has the following members:<BR><BR>fboBooleanAsBit - Specifies that 0 and 1 numbers will be used instead of False and True boolean constants. This option was added to improve compatibility with Microsoft SQL Server. This option is False by default.<BR><BR>fboNoLookupCat - Specifies that no lookup category must be used for the lookup parameters (parameters for which correct lookup information were specified). When this option is on, usual filter condition templates category will be used as if no lookup information was specified. This option affects list of the available conditions for the every lookup field. This option is False by default.<BR><BR>fboHideAdditionalFilter - Specifies that special [Additional Filter] field must be hidden. Value of the [Additional Filter] condition is passed directly to the Filter/SQL without any handling by the FilterBox and it supposed to be in the original Filter/SQL format. For example it could contain "A&gt;5" or other filter<BR>expression. [Additional Filter] feature was added so now possible to <BR>specify filter with any complexity in the native dataset format without <BR>using FilterBox conditions... This option is False by default.<BR><BR>fboHideTemplate_LIKE - Specifies that templates which use LIKE keyword will not be allowed and used. All such templates will be hidden and user will not be able to select them. For example "contains", "begins with".. conditions use LIKE feature and will be hidden when this option is on. This option is False by default.<BR><BR>fboHideTemplate_IN - Specifies that templates which use IN keyword will not be allowed and used. All such templates will be hidden and user will not be able to select them. For example "is in list", "is not in list".. conditions use IN feature and will be hidden when this option is on. This option is False by default.<BR><BR>fboTemplatesStored - Specifies that Templates property is stored with the component. This option is useful if you want to customize templates so they will be different from the default global templates. This option is False by default and Templates property is not stored with the component.<BR><BR>fboAutoSearch - Specifies whether auto search must be performed when filter condition is changed. When this option is on and Filter/SQL is changed, FilterBox will try to lookup the first record which satisfies selected criteria. When FilterBox is used in the search mode (when Filter/SQL of the dataset is not connected to the FilterBox). Please note that not all the conditions that are generated by the FilterBox can be successfully parsed by the TPSCExprEval which is used when auto search is performed.<BR><BR>fboAddConditionBrackets - Specifies that ( and ) brackets must be added to the every individual condition. This option was added as some datasets do not support complex conditions without including them in the ( and ). Also this option is automatically on when "and not", "or not" operations are used between conditions. <BR><BR>fboIncludeCalculated - Specifies whether calculated fields can be used in the filter conditions. This option is False by default.<BR><BR>fboSimpleBoolConditions - Specifies alternative syntax for the conditions which contain boolean fields. When this option is on, syntax "Field" and "not Field" will be used instead of the "Field=True" and "Field=False". This option is False by default.<BR><BR>fboDoubleQuoteInValue - Specifies that #39 character in the values of the filter condition parameters must be doubled, so Filter/SQL parser will not generate error when conditions with #39 symbol are parsed. #39 symbol is ' (single quote) character. This option is True by default.<BR><BR>fboUseUCASEioUPPER - Specifies that UCASE keyword must be used instead of UPPER keyword when conditions with string fields are generated. This option is useful when your dataset does not support UPPER function and supports only UCASE function in the Filter/SQL. This option is False by default.<BR><BR>fboUseRTRIM - Specifies that RTRIM function must be used when conditions with LIKE are generated. This option was added to improve compatibility with Oracle as sometimes it returns character field value with additional space characters which are not actually a part of the value. This option is False by default.<BR><BR>fboUseDollarioIN - Specifies that $ must be used instead of IN keyword when Filter/SQL is generated. This option was added to improve compatibility with Apollo datasets. This option is False by default.<BR><BR>fboUseEMPTYioNULL - Specifies that EMPTY keyword must be used instead of the IS NULL when Filter/SQL is generated. This option was added to improve compatibility with Apollo datasets. This option is False by default.<BR><BR>fboUseCommandTextioSQL - Specifies that "CommandText" property must be used instead of "SQL" as a source of the SQLHead. This option was added to improve compatibility with some client datasets as they store query in the "CommandText" property instead of standard "SQL". This option is False by default.<BR><BR>fboUseADOFieldNameMask - Specifies that special ADO field name mask must be used. ADO field name mask is stored in the SPSCAdoFieldNameMask variable which is set by default to '[%s].[%s]'. This option is False by default.<BR> <BR> <font SIZE="2"><B>See also:</B></font><BR> <A href="TPSCCustomFltBld.Filtered.html">Filtered</A>, <A href="TPSCCustomFltBld.FilterStr.html">FilterStr</A>, <A href="TPSCCustomFltBld.Items.html">Items</A><BR> <BR> <HR> <font SIZE="1">Generated by Putersoft.FreeHelp. Copyright © 1999-2002. <A href="http://www.putersoft.com" target="_blank">puterSoft.Com</A></font></font></font> <CET_ADSENSEF> <script type="text/javascript"><!-- google_ad_client = "pub-5291624188982543"; /* 728x90, A>740=> 04.02.08 */ google_ad_slot = "9704471239"; google_ad_width = 728; google_ad_height = 90; //--> </script> <script type="text/javascript" src="http://pagead2.googlesyndication.com/pagead/show_ads.js"> </script> </CET_ADSENSEF> <CET_FOOTER> <table width="100%" border="0"> <tr> <td colspan="2" bgcolor="#0099FF"><div align="right" class="style1"> <div align="center"><font color="#FFFFFF">You are reading help file online using chmlib.com</font></div> </div></td> </tr> </table> <hr align="left" width="650"><BR> If you want your help file to be removed or added please send e-mail to chmlibcom@gmail.com </CET_FOOTER> </Body></Html>