Oops. I just figured out that part of my request wasn't fully thought
out...
> In fact what it might
> do is rename all searches (including already disabled ones)
> to .xml first and then run the disable batch file. This
> would give the effect of re-enabling previously disabled
> searches
Wow. OK so here is my next set of questions:
1. Can we post this in SF as "disabler.txt" or something. Then add it
to the installer. Then after installed, have the installer rename it to
"disabler.bat".?
2. Then can we add a function to the disabling feature in DQSD that
calls the batch file af
Since the DQSD help window already has an interface to select/unselect
searches, I thought it might be nice to use that to drive the search
removal process instead of a website that Monty has to maintain (although
the delete by category is handy). Attached is a batch file (included
in-line, si
