Norm, I think the search condition is determined by the user on a whim and not knowable when the filter is created/defined.
This feels more like a ... "Hey.. did this happen 4 months ago? What about last week?" kind of a question to me. Not a ... "Every month we will want to know....<bla>" condition. -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. On 9/28/07, Kaiser Norm E CIV USAF 96 CS/SCCE <[EMAIL PROTECTED]> wrote: > Well what do you mean the timeframe is a variable? If you have ticket > 12345, and someone modifies it in March, if you only care to know that > someone modified it in March--not that the ticket was modified 20 or 50 > or 100 times in March--you create one record per ticket per month. If a > record already exists that month, you don't create. If one does NOT > exist, you do create. > > You can make the timeframe as granular as you want. > > It seems like the easiest idea in my mind--rather than table loops, temp > fields, hidden tables, etc. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
