I honestly believe that hiding duplicates should be done at the reporting level. Create 2 groups, one for the ticket and the subgroup would be the time increments (ie months, days, hours... whichever you're trying to report on.)
If you really insist that it be done on the form level, then I'd modify your existing workflow. Assuming days, meaning you don't care for the time portion of the timestamp, I'd have the ticket/date only (no timestamp) as the link between parent and child. That way, if its a new day or different incident, new record gets created. Same day, same incident, update the existing record. So the result is you can update incident xyz 15 times in a day, and only one child record is recorded. If you update that same incident the next day, a new child recorded is created. Hope that helps, Ben Cantatore Remedy Administrator Avon (914) 935-2946 "Wheeler, Dylan" <[EMAIL PROTECTED]> Sent by: "Action Request System discussion list(ARSList)" <[email protected]> 09/28/2007 12:17 PM Please respond to [email protected] To [email protected] cc Subject Unique ID? ** Maybe it's too early in the day but I can't get my head wrapped around a problem. A group here needs to keep track of when records in a form gets modified. They want to be able to search for a date range and come up with the records modified in that date range. Simple enough. The problem I run into is if a record gets updated a month ago, then it gets updated today. If they do their time search for the records that were updated a month ago, it wont show in that list. So I created a table, every time the record gets modified it pushes to a new table and creates a timestamp record. Created a join form between the parent and the timestamp form. Works great except I can't get it to show me only unique records. So if a record gets modified twice in a time period, when they do their search on my join, it will show two of that record. Am I going about this the wrong way? Like Joe I'm trying to stay away from the coffee and tea just doesn't have that same bite heh ------------- Dylan Wheeler Production Control Analyst Principal IT Operations Downey Savings & Loan Association, F.A. Email: [EMAIL PROTECTED] This message and any attachments are for the intended recipient(s) only and may contain privileged, confidential and/or proprietary information about Downey Savings or its customers, which Downey Savings does not intend to disclose to the public. If you received this message by mistake, please notify the sender by reply e-mail and delete the message and attachments. __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
