× 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.



It's funny. In the shops I worked in everyone wanted their reports in GUI
and everything had to be converted to Excel. Nobody wanted printed reports.

Everyone wanted GUI front ends. "Why can't I have GUI screens like I get on
my PC applications.". Now making that happen was damn near impossible but
that was always the request and I don't know how many AS/400 that ceased
being because the management wanted GUI applications and the AS/400 people
told them they couldn't do that.


On Thu, Sep 4, 2014 at 8:59 AM, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

On 9/4/2014 9:56 AM, John Yeung wrote:
Re: Partial laundry list of user rationale for printed output

Was this just an illustration of how difficult it is to get some folks
away from printed output, or does it also imply that your users have
been less resistant to migration away from green screens? And if the
latter, how successful have you been at migrating away from green
screens?

We are 100% green screen by the very vocal choice of our end users and
their managers.

The reason I ask is that the technical issue still remains:

Finally, regardless of how easy or hard it is to learn other UI
technologies and paradigms, in large existing systems, it's easier to
replace printer files one by one in organic fashion than it is to
replace a display file here and a display file there.

Granted, different shops are very different. Maybe in some places, it
is indeed easier to replace display files organically. I struggle to
see how that would be the case, though.

Display files tend to come in clusters, given the modal nature of our
applications which use them. There's a panel to enter the customer
number, a panel to verify the sold to / ship to information, a panel to
handle purchase order number and other ancillary information, a panel to
enter items, a panel to verify the order and a panel to ask 'are you
sure?' In this sort of environment, it's really difficult to extract
just one of those panels and make it a web page.

Printed reports tend to be less like that, but still the tendency is
there. No one wants to get their weekly aged trial balance on the web,
the delinquent customer list in Excel, the customer list in PDF and the
top ten dollar amount delinquents on their dashboard. All of those
reports are related, at least in the mind of the person tasked with
dealing with them.

The technical problem is less, but the procedural problem still exists. :-(
--buck
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



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.