This customer is running AREV3.1 on a Novell 4.0 network with

the workstations using windows 3.1

This application has been runing without problems until recently.

The SELECT, SSELECT and COUNTROWS commands are producing the same results with the same selections, but the results are different when multiple WITH selections are used. Consider the following examples:

COUNTROWS STORES

  =======]  counts 17078 total stores (information is ok)

COUNTROWS STORES WITH RECORD_STATUS "A"

  =======]  counts 11403 active stores (information is ok)

COUNTROWS STORES WITH STORE_STATUS "13" "1" "4" "5" … "25"

  =======]  counts 15260 stores with the listed statuses (info ok)

COUNTROWS STORES WITH RECORD_STATUS "A" AND WITH STORE_STATUS "13" "1" "4" "5" … "25"

  =======]  counts 14840 active stores with the listed statuses

* The 14840 count is wrong because there are only 11403 active stores *

It appears that when multiple WITH statements are used it reports bad results.

I have also use the following variation with the same bad results:

COUNTROWS STORES WITH RECORD_STATUS EQ "A" AND WITH STORE_STATUS EQ "13" "1" "4" "5" … "25"

The RECORD_STATUS and STORE_STATUS fields are not indexed and are defined at VARCHAR at the maximum size.

Any suggestions on how to fix this will be greatly appreciated.

Thanks……

Hmmm. Sounds like may be same problem I described a week or so ago under topic "Btree.Extract Broke …..". In that case both Btree.Extract and TCL SELECT ok with single-field searches, but failed with multi-field selections.

What is the key length and the dictionary definitions for the key. Re the two fields for selection, are they single-value or multi-value fields?

Try not using the shorthand and implied claused and flesh out the statement with full with, ands, ors and parentheses and see if that makes a difference. ARev 3.10 and 3.111 interpret R/LIST selection criteria different from all other version.

akaplan@sprezzatura.com

Sprezzatura, Inc.

View this thread on the forum...