Its stored in the client variable so I dont think its a client side cookie.
We use client variables that are stored in db for most of our applications.
If its a bad practice then we will create new thread as it might help me and
others. But at this moment my need is based on verity and how can i
Well, the data for the DB is something that is specific to the app,
not the client. Store it in the APPLICATION scope, not in the CLIENT
scope.
-dhs
Dean H. Saxe, CISSP, CEH
[EMAIL PROTECTED]
Dissent is the purest form of patriotism.
--Thomas Jefferson
On Mar 5, 2007, at 10:45 AM,
Yes, what you're suggesting
is a good idea, however, I would go a bit
further and place both Reason_Text and State
in that first custom field by simply delimiting
the data. Change the search page so that
if the user chooses a state other than all,
the following would be added to your
Change the search page so that if the user chooses a state other than all,
the following would be added to your Verity query: custom1 CONTAINS [state]
By verity query, do you mean the query which is used for building
collection? If it is, then dont you think it will be too much to index the
