>I am having trouble Using OR and AND in select and list statements. It
>suggested to me that the problem had to do with multi-valued data. I
>able to select each component of the complex select/list by itself but
>connected with AND/OR.
>I am rather new to Arev, but have been working with PICK for years. Is
>there a USENET group especially for AREV?
comp.databases.pick is pretty much the newsgroup that most of the
AREVer's hang out on. Myself and at least half a dozen other good AREV
programmers are very willing to answer any questions that we can. For
your particular problem, most of us would probably need to know what it
is that you're trying to do. A LIST/SELECT statement with definition
of the types of fields that are involved in the WITH statements would
be enough to tell you what you're statement is going to do. Don't
forget to include sample data.
In general, if you keep in mind that LIST and SELECT work basically
with the record keys. If ANY value of a multi value field satisifies
the conditional test then the record ID is included. Example:
SELECT filename WITH mfield3 = "STICK" AND WITH mfield4 = "GREEN"
Result: You will have record ID'S 001 and 002.
SELECT filename WITH field2 = 'PEAR' AND WITH mfield3 = "PAPER" OR WITH
mfield4 = "RED"
Result: You will have record ID's 002 and 003 because of the OR
To get the result of ('PEAR' and 'PAPER') or ('PEAR' and 'RED') there
would be a couple of different ways to approach this. You could make
this two selects instead of one (first being 'PEAR' then second one for
'PAPER' or 'RED') or you could make a symbolic that tests for the
conditions. I'm sure there are many other ways but these two are the
ones that I use the most depending on what I'm going. If it's a quick
and dirty report, one time, I'll go for the symbolic (I use the same
symbolic name for all my quick and dirty reports so I don't fill the
DICT file with clutter)
This description is a little on the "light" side because you said you
were fairly new to AREV. This does not account for duplicate values in
the multi-valued fields, and it also does not go into detail about the
record ID's returning the key value PLUS the value level, but I think
I've covered ONE aspect of working the Multi-value fields. There is
alot more to this than what I've covered.
I'd be happy to answer other questions in email but you'd get a better
cross reference from some of the other AREVer's if you keep posting
Hope I've helped some.
Bob (Oh! It's YOU, Bob!) Woodward :)