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



What I have ended up doing (and, so far, tests are successful) is using all
three values from the RTNCSRLOC (record format, field name, & relative
position within field).  If the AID byte = x'F1' *AND* the record format
name and field name are matched to my values *AND* the relative cursor
position within field is equal to the length of the field (i.e. the cursor
is in the last position of the field), I am assuming that CHECK(ER) caused
return to the program.

Thanks to all who volunteered suggestions!

Dan Bale
SAMSA, Inc.
989-790-0507
DBale@SAMSA.com <mailto:DBale@SAMSA.com>
  Stanley Cup Finals lower bowl tickets at Joe Louis Arena: $500
  Official Red Wings jersey: $150
  Octopii to drop splat in front of Irbe: $22 each
  TEN Lord Stanleys: PRICELESS!


-----Original Message-----
From: rpg400-l-admin@midrange.com [mailto:rpg400-l-admin@midrange.com]On
Behalf Of Carel Teijgeler
Sent: Thursday, June 20, 2002 3:30 PM
To: rpg400-l@midrange.com
Subject: Re: differentiate between Enter vs. CHECK(ER)?


Hello  Dan,

Instead of testing the AID bytes, which get the same value after pressing
enter or leaving a field with CHECK(ER), you can calculate the cursor
position using the CURLOC keyword;
or use the RTNCSRLOC and test the second value on this keyword for the field
the cursor was in. I do not know, if the system returns the fieldname which
you have atributed with CHECK(ER), as the user intended to leave that field.

Regards.
Carel Teijgeler



As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.