FAQ

Will it work with non-BDE datasets?
 
FilterBox works with any TDataSet descendant. FilterBox is fully customizable and can be setup to generate filter in any format, also all filter conditions are definable. If you will find any incompatibilities with your version of third party dataset we will fix it immediately. 
 
What the difference is between the Standard and Pro versions of PSC FilterBox?
 
Pro version will include additional components allowing end-user customization of the FilterBox settings, component for end-user grid colors/fonts customization depending on the record set (record set is defined with FilterBox). Color and Font editors like MS FrontPage, Pro version of Calendar (which shows international holidays, has MS Money month popup,...) and some other components. Both Std and Pro versions come with full source code.
 
Is there other operators like "Starts with", "Ends with", "Contains" or it has to make it by user?
 
These operations are in the templates. By default in V0.96B they are not shown because most of the datasets doesn't support LIKE clause in filters. To show them you need to assign '0,1' to AllowedUsageIDs property of the FilterBox. Starting from V0.97B we added our own filtering routines and now it's possible to use LIKE in filters of any dataset, so "Starts with", "Ends with", "Contains" available for use by default. 
  
Does it support Access date conversion (i.e. Access date format is #mm/dd/yyyy#, wrote as see in italic letters, and any conversation that BDE is doing itself?
 
Yes, it supports Access date format. Date format can be specified with FilterDateTimeFormat, SQLDateTimeFormat, DisplayDateTimeFormat properties. Also # can be specified instead of ' starting from the V0.97B (There is OnQuoteStr event). 
 
Can you change operators and all strings on form in some other language-using resource file?
 
Yes. Currently we support the following languages: English, Spanish, German, Greek, Czech, Russian. New language is added simply by creating of the localized version of PSC_ENG.INC file, which includes all string constants (as resource strings) used in our products. We worked close with some of our international customers and all the problems with localization/customization depending on the language and country locale settings seems to be solved now.
  
In your demo (what I've seen) there is no print option-so the result of query is TQuery component or some TTable (created on disk or in memory?)? Could that be changed or customize?
 
FilterBox generates filter in it's FilterStr property and query in it's SQL property. You can get the value and use it as you wish. Also there are HookSQLProp and HookFilterProp properties which implement automatic integration with Filter/SQL property of the datasets.
  
Is FilterBox component compatible with Delphi 5 or you have to buy Delphi 4 and Delphi 5 separately? (we are using both platforms!)
 
Our products are compatible with Delphi 3,4,5, C++ Builder 3,4. You don't need to buy separate versions. We offer free life time updates, upgrades and bug fixes. This means you won't need to pay us for the new versions forever!