Is DQSD still
loading *all* the searches upon startup, even the ones which are disabled?
The real benefit of being able to disable searches - other than
simplifying the menu - is to save all the overhead of loading/maintaining all
the objects created by the unwanted searches, not to mention the time to load
them.. Is this something that is achievable in the current
design?
Monty
_/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/
_/ _/ _/
Monty
Scroggins
Broadband Data Systems Engineering
(BDSE)
MCI Worldcom
