|
From: smorrison@xxxxxxxxxxxxxxxxxxx There is a lot of difference between what I can't do on WDSC that I can do in SEU versus what I can't do in WDSC that I can do in PDM.
Other than the fact that the WDSC GUI search doesn't exactly match the PDM green screen search, what complaints do you have?
How do I do the string searches in WDSC vs PDM - with the same speed, and with the ability to get the printed list I get in PDM?
Steven, if the worst complaint you have is that a client/server application isn't as fast as the same thing run natively on the host then I think you're reaching a bit. I WILL say that not being able to print the list is a problem, but that enhancement is already on the list. My guess is that the WDSC developers aren't real big on printed lists. Other than that complaint, though, the search capability in WDSC is more powerful, since it allows you to span multiple files and libraries, and is more productive since it allows you to review the lines in context and open the members with a double-click, something you simply can't do in PDM. Yes, it's somewhat slower, but that's intrinsic in a client/server environment. Personally, I don't notice the speed difference unless I go over multiple libraries. As far as your issue of liking to see totals for impact analysis, look at the search results view: it shows "xx matches in yy members". That's a pretty good summary. And once they get the copy/paste to work in the search results view, I think your other issues will be pretty much moot. Joe
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.