refresh field value

[Peter Bateman]

Lorry:


>From: Lorry Litman <LLitman@exchange.hsc.mb.ca>
>To: 'Peter Bateman' <pfbcs@hotmail.com>
>Subject: RE: refresh field value
>Date: Thu, 10 Jun 2004 11:59:08 -0500
>
>Hi Peter,
>
>Why would I need to commit the query transaction?
>How would I know?
>Query is the default transaction name for query. I have defined it for 
>query
>and process. This is something I've almost always used on reference files 
>so
>the update transaction doesn't start on lookups of the field statement.
>If I have to commit the transaction, I suspect I would probably want to
>create a separate transaction for that one reference file.
>

  I can understand that you don't want your PUTs to be translated
  to actions in a long UPDATE transaction. However, in this case you
  want post start of QUERY changes to be diisplayed.

  I woulld do the lookups in the UPDATE transaction which I believe
  should be commited  after the UPDATE procedure in the subscreen.
  Just to sure you could put the COMMIT UPDATE statement just
  before your get after the RUN SCREEN.

  Use PUSH RETURN rather than  the RETURN verb to get out of the subscreen.

  The difference is the RETURN verb returns to the calling screen without
  completing the procedure iit is in. Whereas ther PUSH RETURN allows
  the end of procedure process to complete including commit the  UPDATE
  transaction.

  Regards,
  Peter Bateman

_________________________________________________________________
Add photos to your messages with MSN Premium. Get 2 months FREE*  
http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=http://hotmail.com/enca&HL=Market_MSNIS_Taglines