RE: MAPVAL issues

The only other possibility I can think of is that the data structure definition is messing with it somehow. Maybe test it without that if you can.

Scott


-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Mark Murphy/STAR BASE Consulting Inc.
Sent: Wednesday, July 30, 2014 3:11 PM
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: RE: MAPVAL issues

See below

Mark Murphy
STAR BASE Consulting, Inc.
mmurphy@xxxxxxxxxxxxxxx


-----Scott Mildenberger <SMildenberger@xxxxxxxxxxxxxxxxxx> wrote: -----
To: "RPG programming on the IBM i (AS/400 and iSeries)" <rpg400-l@xxxxxxxxxxxx>
From: Scott Mildenberger <SMildenberger@xxxxxxxxxxxxxxxxxx>
Date: 07/30/2014 04:59PM
Subject: RE: MAPVAL issues

We have screens coded just like you do except they don't have the DATSEP keyword which shouldn't matter as that defaults to '/'
if not specified. Do you only get the error if you key a blank in the field?

No

If you just Field Exit through the field does it also give the error?

Yes

I know I have sometimes had issues with this but we do have a lot of
programs that use it. Do you get the error on the EXFMT statement when it returns to the program or at a later step when you use the field?

When I try to use the field.

Can you look at the value coming back from the EXFMT in debug?

Yes, it is blank

I just noticed your field is I for Input, all of ours are either
B(oth) or O(utput). Don't know if that has anything to do with it.

Started out using B.