Pete and Eric both made very good points.  It isn't as simple as
search <word> in <listname> because <listname> is not like a file
you use GREP on to find occurences.  You've got to find the individual
messages that match the search specifications and create a subset of
the list archives that includes only the messages that contain those
specifics.  Then you have to create an index by subject so you can
PRINT and INDEX.  It's just more complicated than "where are all of
the occurences in LSTOWN-L of the string 'database command syntax'?"
 
My only question is how much trouble would it be to change the command
language to meet the ANSI SQL standard (or does it?  I'm more used to
Microsoft SQL, which is another animal entirely).  Obviously it is
already most of the way there, as it is a "structured query language."
 
Like Pete, I am only musing and not really suggesting that a major
change ought to be made in the software...:)
 
(BTW, Pete, that "et -L" in your sig just about broke me up...:)
 
BITNET:  NBRINDLE@INDYCMS  --------------------  Internet:  [log in to unmask]
Nathan C. Brindle, Student Activities Office
Indiana University Purdue University Indianapolis
Staff Advisor, Alpha Phi Omega Nat'l Service Fraternity, Tau Omicron Chapter
List Manager, ACCESS-L, BRTHPRNT, EXCEL-L@INDYCMS and other lists
Disclaimer:  My opinions are my own.  Indiana University can speak for itself.
------------------------------------------------------------------------------