Field validation in DFU (Was: Thats all folks!)

["Simon Coulter" <shc@xxxxxxxxxxxxxxxxx>]

Hello Rob,

You wrote:
>For example, you could define a file in IDDU and restrict the values for
>certain fields.  Then if you ran the S/36 equivalent of UPDDTA it would
>prevent you from doing so.  When we migrated that to the AS/400 that was
>dropped.  The DDS keywords that were supposed to do the same thing were
>only there to make SDA try to adopt some of these for screens.  They
>were ignored by UPDDTA.  Now SQL with constraints seems to have plugged
>that glaring hole.

UPDDTA does the same thing (and as far as I recall always did).  If I
code DDS validity checks in a database file definition they will be used
by the display screen generated by DFU.  UPDDTA is intended for quick and
dirty fixes but still imposes DDS validity checks.  If you want more
control then you must create a permanent DFU.  You can save the generated
DDS and edit it.  Then create a DFU display file using the CRTDFUDSPF
command.

Regards,
Simon Coulter.
--------------------------------------------------------------------
   FlyByNight Software         AS/400 Technical Specialists

   http://www.flybynight.com.au/
   Phone: +61 3 9419 0175   Mobile: +61 0411 091 400        /"\
   Fax:   +61 3 9419 0175   mailto: shc@flybynight.com.au   \ /
                                                             X
                 ASCII Ribbon campaign against HTML E-Mail  / \
--------------------------------------------------------------------