Hi Amy,
 
I may be experiencing problems similar to or related to your problem. I am
having problems with Advanced Query searches particularly with Object
Packages. Recently, what I have been trying to achieve is to combine several
object packages into one using AQ. Per advice from tms I've changed "and"
relations to "or," which meant that I went from finding nothing in my search
to getting nearly the entire collection, which far exceeds the number of
objects within the Object Packages I created.
 
I am not an application nor SQL  expert, but something is not functioning
correctly with AQ searches.
 
Scott Nacke
Assistant Registrar/Rights and Permissions Manager
Seattle Art Museum
 
 
-----Original Message-----
From: Amy Noel [mailto:[log in to unmask]]
Sent: Monday, November 25, 2002 4:02 PM
To: [log in to unmask]
Subject: "and not" queries
 
 
Hello fellow TMS Users,
 
I'm wondering if we are one of a few TMS users for whom some query functions
do not work.  Particualry,  "and not" queries do not work on large number of
records and CLOB fields, like object packages.  This means that end users
(who do not use SQL worksheet) cannot eliminate an Object Package from a
larger selection or query "and not *" on some fields.
 
Is there anyone who has this problem and found a way around it within the
application?  I don't see our average TMS user learning SQL.  This is
becoming more of an issue for us as our number of in-house staff learn and
use TMS continues to grow.
 
Thanks,
Amy Noel
CIS Application Manager
The J. Paul Getty Museum