Re: Methodology conflicts.

 Isn't that difference between cycle-driven and event-driven?  Event-driven
programming requires immediate processing of data because one never knows
whither goest the user.

My experience so far says event-driven is a good thing.  Opens up so many
more choices for the programmer.

---------------------------------------------------------
Booth Martin   http://www.MartinVT.com
Booth@MartinVT.com
---------------------------------------------------------

-------Original Message-------

From: midrange-l@midrange.com
Date: Wednesday, November 06, 2002 03:57:50 PM
To: 'Midrange Mailing LIst'
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