× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



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.

Joe


From: Rick.Chevalier@xxxxxxxxxxxxxxx


Joe Pluta wrote:
Me, I'm talking about having different filters for different
applications within an application suite, as well as for different
versions for historical or comparative purposes, so I need lots of
filters in one connection.

Joe,

I've been using the connection per project for some time now and one of
the things I really like is that I can easily open the connection for an
old project and see what objects were used.  It makes going back in time
much easier.

I also think it simplifies the clutter of multiple filters.  I do use
filter pools, but my main connection to our development box is still
cumbersome to navigate.  It contains filters for each of the source
files in my library (27 files, each for a different application +
personal development/historical files) filters for members of my
development team, and filters for our production source.  Each in a
separate pool.  I much prefer a project connection where I can filter
just the source files I will need.  It's a much smaller list to wade
through.

Because connections are the top level of RSI it's easy to find things if
the names are descriptive.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.