Re: Emulator Closing Event

   Which can be handled by keeping images of the data before and after and
   checking for changes.  We even did this on a /36, but it's much easier in
   RPG IV.  Paul Tuohy gave a brief overview of the technique at COMMON
   (others probably have, as well).  The only thing you have to figure out
   is"What do I do if the images aren't the same?"  Usually just redisplay
   the changed record with an info message.

 Jerry C. Adams

   kristof.anthonis@xxxxxx wrote:

 I think you should never LOCK a record to fill your screen.
 I use a CHAIN(N) first so the program doesn't lock the record. Then
 after the user presses ENTER, CHAIN again (with lock now) and
 immediately UPDATE.
 So when the user closes their session, the record is not locked.
 Only disadvantage; 2 users can open the record at the same time without
 knowing that from each other.


 -----Original Message-----
 From: rpg400-l-bounces@xxxxxxxxxxxx
 [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of
 Chris_Bougher@xxxxxxxxxxxxx
 Sent: woensdag 15 juni 2005 15:50
 To: rpg400-l@xxxxxxxxxxxx
 Subject: Emulator Closing Event


 How can I tell within my program if the user has closed their emulator
 session? We have situations where a record is locked and the users are
 closing their emulators and this is causing data integrity issues.

 Thanks
 Chris Bougher