Tim ~

V4.25/D5/XP Home

From the help for FilterOptimizeLevel:
"You may examine this property at any time after the Filter property is assigned a valid
filter expression - you do not necessarily have to set the Filtered property to True. "

This worked with earlier versions of DBIsam. Now with the current version it does not
anymore -
I have to actually apply the filter for it to see the facts or else it always returns
foNone - see
snippet below.

The query plan gets it right - fully optimized.

Kai


snip
 
dbit.open;
dbit.Filter := 'record_status = ''A''';   // now a case sensitive index

// if I comment the line below out, it always returns foNone - foFull otherwise!
dbit.Filtered := True;                                   
case dbit.FilterOptimizeLevel of
 foNone:      ShowMessage('None');
 foPartial:    ShowMessage('Partial');
 foFull:        ShowMessage('Full');
end;
dbit.Close;

Kai,

<< This worked with earlier versions of DBIsam. Now with the current version
it does not anymore - I have to actually apply the filter for it to see the
facts or else it always returns foNone - see snippet below. >>

It's now a documentation bug and I'll make sure that it is fixed.  The
reason for the change was this:

http://www.elevatesoft.com/scripts/incident.dll?action=viewrep&category=dbisam&release=4.05&type=f&incident=1681

--
Tim Young
Elevate Software
www.elevatesoft.com