Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 9 of 9 total |
A little filter problem |
Tue, Aug 1 2006 9:57 AM | Permanent Link |
"Jose Eduardo Helminsky" | Tim
Another little issue. There is a table with a field called FLG and some records were populated with * If I call SQL statement SELECT * FROM TABLE WHERE FLG='*', it works as expected but if I apply a filter FLG='*' on a table it does not work. Eduardo |
Tue, Aug 1 2006 10:16 AM | Permanent Link |
"Ralf Mimoun" | Jose Eduardo Helminsky wrote:
> Tim > > Another little issue. > > There is a table with a field called FLG and some records were > populated with * > > If I call SQL statement SELECT * FROM TABLE WHERE FLG='*', it works as > expected but if I apply a filter FLG='*' on a table it does not work. Please explain "does not work". Do you get all records or no records at all? Did you set Filtered to True? Ralf |
Tue, Aug 1 2006 10:41 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Jose
Somewhere at the back of my mind is a memory that * in a filter is a wildcard like DOS Roy Lambert |
Wed, Aug 2 2006 6:16 AM | Permanent Link |
"Jose Eduardo Helminsky" | Ralf
> Please explain "does not work". Do you get all records or no records at > all? "Does not work" means, I get *ALL* records instead of only records with '*'. > Did you set Filtered to True? Yes Eduardo |
Wed, Aug 2 2006 6:17 AM | Permanent Link |
"Jose Eduardo Helminsky" | Roy
> Somewhere at the back of my mind is a memory that * in a filter is a > wildcard like DOS It can be my mistake using * as a field content but if this is a wildcard, it is not documented. Eduardo |
Wed, Aug 2 2006 9:33 AM | Permanent Link |
"Ralf Mimoun" | Jose Eduardo Helminsky wrote:
.... > It can be my mistake using * as a field content but if this is a > wildcard, it is not documented. It is, see "Setting Filters on Tables and Query Result Sets" in the help file. You have to add foNoPartialCompare to the FilterOptions to get the behaviour you want. Ralf |
Wed, Aug 2 2006 10:14 AM | Permanent Link |
"Jose Eduardo Helminsky" | Ralf
Ok, I´ve checked the help and found this issue. Thanks for your help Eduardo "Ralf Mimoun" <nospam@rad-on.de> escreveu na mensagem news:142A64CD-F3B8-4D66-9095-FA8CB2D27634@news.elevatesoft.com... > Jose Eduardo Helminsky wrote: > ... >> It can be my mistake using * as a field content but if this is a >> wildcard, it is not documented. > > It is, see "Setting Filters on Tables and Query Result Sets" in the help > file. You have to add foNoPartialCompare to the FilterOptions to get the > behaviour you want. > > Ralf |
Wed, Aug 2 2006 2:02 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Eduardo,
<< There is a table with a field called FLG and some records were populated with * If I call SQL statement SELECT * FROM TABLE WHERE FLG='*', it works as expected but if I apply a filter FLG='*' on a table it does not work. >> Include the foNoPartialMatch filter option in the FilterOptions property. -- Tim Young Elevate Software www.elevatesoft.com |
Wed, Aug 2 2006 3:08 PM | Permanent Link |
"Jose Eduardo Helminsky" | Tim
> Include the foNoPartialMatch filter option in the FilterOptions property. Got it Thanks Eduardo |
This web page was last updated on Tuesday, September 17, 2024 at 04:19 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |