|
One caveat when using multiple filter strings is that the order of items in the filter tree is dependant on the order of the filter strings. I believe this is an issue that the WDSC team has on their list. wdsci-l-bounces@xxxxxxxxxxxx wrote on 06/07/2006 02:10:03 PM:
Joe, I get it now I think. Even if you used a connection it seems like you would end up with pretty much the same scenario you have now. BTW, are you using member filters? I was able to create a single member filter over two different libraries. I used the same source file but I don't think that really matters. I created the filter with the first selection criteria then changed it (R-click -> Change) to add a new filter criteria. I'm not sure it's exactly what you need however, as I can't tell which library the members are really in. I didn't notice any duplicates but that might be an issue too. Rick-----Original Message----- From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Joe Pluta Sent: Thursday, July 06, 2006 12:57 PM To: 'Websphere Development Studio Client for iSeries' Subject: Re: [WDSCI-L] Enhancement Request That's great, Rick, but it still doesn't help me. When I'm working on a single task, I may need to access programs from order entry, purchasing and AP, as well as some utility programs. The way the application suite is set up, each application is easily filtered using a prefix on the member name (such as ORD* for order entry). However, there are maybe twenty different applications. Add to that the fact that I typically have at least two different filters for a given prefix, one for production source and one for test source, and you can see that I can quickly end up with a lot of filters. Add in variants for multiple versions or client custom code, and you can get pretty full pretty quick, Now, if filters had the ability to add LISTS of selection criteria (such as all ORD*, PUR* and SYS* members in libraries RV50PROD and REV50TEST) then it might be a little easier. JoePrivileged and Confidential. This e-mail, and any attachments there to, is intended only for use by the addressee(s) named herein and may contain privileged or confidential information. If you have received this e-mail in error, please notify me immediately by a return e-mail and delete this e-mail. You are hereby notified that any dissemination, distribution or copying of this e-mail and/or any attachments thereto, is strictly prohibited. -- This is the Websphere Development Studio Client for iSeries (WDSCI- L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.
##################################################################################### Attention: The above message and/or attachment(s) is private and confidential and is intended only for the people for which it is addressed. If you are not named in the address fields, ignore the contents and delete all the material. Thank you. Have a nice day. For more information on email virus scanning, security and content management, please contact administrator@xxxxxxxxxxxx #####################################################################################
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.