Re: Methodology conflicts.

This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
I would argue that a poorly defined 5250 application can do the same.  For
example update the inventory balance in the item master but not the
items-by-warehouse until the next screen.  Then someone shuts down the
5250 screen.

Cases like this may inspire you to look harder at journalling, commitment
control, referential integrity and triggers.

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin




"Shields, Ken" <kenshields@ppg.com>
Sent by: midrange-l-admin@midrange.com
11/06/2002 03:52 PM
Please respond to midrange-l

        To:     "'Midrange Mailing LIst'" <Midrange-L@midrange.com>
        cc:
        Fax to:
        Subject:        Methodology conflicts.


Hi Everyone.
                 Have had quite a few episodes, where data was not updated
on the /400, because of the windoze , or
shall I say conflicting operational methods between legacy apps, and
windows.
                 Let me explain:
                 Once upon a time, all communication with a computer was
done with the Enter key. This included character mode
                 mid range machines as well.
                 With the advent of windows, and the ability to minimize
screens, there now exists a much greater liklihood, that when
                 a window does re-appear, the operator is so engrossed
with the mouse methods, apps are examined and windows are
                 closed, without first hitting the Enter key...(Emulation
window).
                 Most MS apps, and other software prompt the operator with
a 'Do you want to save...' litany, or the app dynamically
                 updates data in place(some Access functions).
                 I was just curious to know, how many other people in this
group, have run accross this same type of problem.?
It's not going away...
Thanks

Ken Shields

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.