Joined: 21 Jan 2008 Posts: 1 Location: Oklahoma, USA
It has been several years since I coded my last MFS map and I could use a little help. I created a new app and it was similar enough to an old one that I was able to use a copy of the old MFS map to create the new map. The basic setup parms are the same for both maps. When I execute the other transaction, the autoskip works fine. However, when I execute my transaction, the cursor stops on the next field, instead of skipping to the intended field.
ACTION DFLD POS=(10,02),LTH=1,ATTR=MOD
CTLNBR DFLD POS=(10,04),LTH=6,ATTR=(PROT,MOD)
MONTH DFLD POS=(10,11),LTH=2,ATTR=(PROT,MOD,NUM)
DAY DFLD POS=(10,14),LTH=2,ATTR=(PROT,MOD,NUM)
YEAR DFLD POS=(10,17),LTH=2,ATTR=(PROT,MOD,NUM)
ASSIGNTO DFLD POS=(10,21),LTH=6,ATTR=MOD
METHOD DFLD POS=(10,30),LTH=1,ATTR=MOD
This code is functionally identical to the other transaction. When I enter a value for ACTION in the new transaction, the cursor jumps to CTLNBR instead of ASSIGNTO, like it does with the old transaction. I tried removing the MOD parm from the fields between ACTION and ASSIGNTO and got the same results.
I did a search and found one other post having to do with Autoskip, which the OP did not use.
Specifies whether the field should have the numeric attribute. The numeric attribute specifies that the Numeric Lock feature (automatic upshift of data entry keyboard) will be used by the 3275/3277 or 3276/3278. If NUM and PROT are specified for the field, the auto-skip feature is used. That is, upon entry of a character into the last character location of an unprotected field, the cursor automatically skips the field with the NUM and PROT attribute specifications and is positioned to the first character location of the next unprotected field. If an undefined field, as described in the ATTR= parameter, follows the filled unprotected field, the auto-skip feature is used. This parameter, in conjunction with the PROT parameter, is used to lock the COPY function. See "PROT" for details.