Alex,

I would approach the problem from a very different angle.

Make routine and potentially dangerous activities as easy as possible,
but leave room for verification steps in the process.

I would try to:

1) define the query that you want to use to delete the data from each from with.
2) Create an ARS form that holds the form and Query information in
character fields.
3) Use a filter and the "Application-Query-Delete-Entry <form>
<qualification_string>" $PROCESS$ or Run Process action  to do the
dead.

4) If you want to review the records manually first, then use an
advanced Table field to point at the form(s) in question and review
the matching records first. then push the "Delete" button in the User
Tool.

Should not take to much effort to put together an "admin only" form to
hold the data and to be used as a UI for the display/delete of the
records too.


Now if you really need to automate this with the driver program. Then
write a form that you can use Driver to submit a record to. Have that
submit trigger filters that loop over the configured information and
deletes the data it finds "blindly". (I mean without a user review of
the data.)


Just be warned the first data row that you delete that you should not
have deleted... well... that will be a problem. So be sure that your
qualifications work, and are tested after every change. (Just a word
to the wise.)


--
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/06, Alex Straph <[EMAIL PROTECTED]> wrote:
Over the last couple of months, six of our servers have been "invaded" with
several hundred entries each of dummy data over several forms.  This data
is causing performance issues so of course I have been tasked to find and
get rid of it.

The good news is that the corrupt entries have consistent data meaning that
I could use a search filter to weed out the data.  Earlier, I have been
manually removing entries myself, only to find that these entries have
risen from the ashes.  It has become a pain to do each an every single week
so I need to use a driver script to specify what to delete.  I have decided
on using a driver script as a temporary fix until I get to the bottom of
the corrupt data issue.

One question though: there is only one option in driver that will allow you
to delete entries, and that is de.  From what I gather, it deletes entries
based on field Id 1.  Is there any way to delete entries based on other
parameters OTHER than field Id 1?

Thanks.

Alex.

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org


_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org

Reply via email to