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



The pressing of F4 does not activate the marker READC uses to indicate a
subfile record has been changed.  You must calculate the subfile record on
which the cursor was positioned when F4 was pressed and then turn on
SFLNXTCHG so READC will identify the record.

Of course, since you already know which subfile record is involved, you
could just invoke your editing routine after the F4 processing is complete.

The algorithm I use for calculating the subfile relative record number is as
follows:
FDSPF001   CF   E             WORKSTN SFILE(SUBFILE:RRN1)
F                                     INFDS(DSPFDS)

DDSPFDS           DS
D  DSCRSRPOS            370    371B 0
D  DS1STSFRCD           378    379B 0

C                   EVAL      RRN1 = (S1ROW - <1st sf line>) + DS1STSFRCD

S1ROW is defined in the DDS as follows:
RTNCSRLOC(*MOUSE &S1ROW &S1COLUMN)
S1ROW          3S 0H

If you have multiple columns, you must determine on which column the cursor
is and add to the RRN1 calculation as needed.

Hope this helps.

Donald R. Fisher, III
Project Manager
The Roomstore Furniture Company
(804) 784-7600 extension 2124
DFisher@roomstoreeast.com

<clip>
All I want to do is be able to do an F4 on the reason and have the code
returned from a selection list to the correct subfile line selected from
and if there are any errors - eg the user enters in the wrong code then
that line is highlighted and not processed and the subfile is re-written
showing the errors and removing those items already processed.
<clip>


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.