Icon View Incident Report

Serious Serious
Reported By: Joe Real
Reported On: 1/14/2005
For: Version 4.16 Build 1
# 1945 <> String Field Comparisons on Tables Not Using ANSI Standard Locale Returns Incorrect Result

I have a table with fields containing string fields of length 1, for example the Field name 'Status' with field size of 1 string, and has a case sensitive index of the same name. My only possible values for this field are 'A', 'D', 'M' and 'G'

I have a total of 255 records, of which 227 are 'A', 4 are 'D', 2 are 'M' and 2 are 'G'.

Next I issue a filter Status <> 'A' it returns me 255 records instead of 28 and I can see all the 'A' values when this filter is in effect. The same number of records if I issue a filter Status <>'M' and Status <> 'G' However, the table filter works perfectly for the filter: Status='A' gives back 227 records.

As a work around, the following works perfectly for an equivalent filter:

NOT (Status = 'A') instead of Status<>'A'
NOT (Status = 'M' or Status = 'G') instead of Status <>'M' and Status <> 'G'

Comments Comments and Workarounds
Workaround is as described by Joe.

Resolution Resolution
Fixed Problem on 1/18/2005 in version 4.17 build 1