Thank you, Ingo!
I will have a look at this after the summer. (This is my last day at work before summer vacation.)

/ Jenny

Note: Ingo's example code would populate format and deformat triggers for all fields, and you might only want to apply the change to fields with the required data type. Also, you might want to consider external variations (in UXFIELD). I would recommend doing a clean up and making a backup first if you do this.

Regards,
David

Hi Dakerman

You are right :-)

Thanks for clearifying this.

Ingo

Hi Jenny,

For Date-fields I do not prefer to use the field syntax property ENT() . 

For Date-fields (dataype D) you can use 1 field LAYOUT property:  DIS(yyyy-mm-dd).

Or you can use another Layout format like DIS(yymmdd) or DIS(yyyymmdd).

You can also apply Field Layout format for datatypes DateTime and Time .

Jip

Are your sure, that ENT is the rigth way to tell UnifAce which entry formats fopr DATE-fields are allowed? :-)

From documentation:

If you use the ENT shorthand code for data entry, use the ENT(DMY) format if you want 4-digit year input (for example, 01-01-1997). The format ENT(YMD) only permits the entry of two digits (for example, 97-01-01).

So if you need other format then in DIS defined, you have to code the FORMAT/DEFORMAT-trigger. With the use of globale procedures, this can be done in an elegant way :-)

Ingo

Thank you for your reply, Ingo!

I have also read this line in the Uniface Library:
If you use the ENT shorthand code for data entry, use the ENT(DMY) format if you want 4-digit year input (for example, 01-01-1997). The format ENT(YMD) only permits the entry of two digits (for example, 97-01-01).
And that is why I was so surprised that ENT(ymd) still did allow a 4-digit year input (but only when I type it all in a row, yyyymmdd, not yyyy-mm-dd).

Maybe we will have to consider the use of global procedures after all, even though it would mean that we would have to put code (at least calls) into a lot of forms...

/ Jenny

Hi Jenny

About the globale procedures:

Do you have allready code in the DEFORMAT-trigger?

If not, there is a very easy solution to populate the trigger. Just create a from with entity UCFIELD painted in it. Code a loop over all occurences in UCFIELD.

You can code a more complex procedure if required. e.g. check for a place to put new new CALL if there is allready code in the trigger

Ingo

ENTRY LP_POPULATE
  $FMT_TRIGGER$ ="call SF_FORMAT(%%"%%")"   ; Whatever you want call
  $DFMT_TRIGGER$="call SF_DEFORMAT(%%"%%")" ; Whatever you want call
  clear/e "UCFIELD"
  U_VLAB.UCFIELD/init="your_modell"
  retrieve/e "UCFIELD"
  v_I=0
  WHILE(1)
    v_I=v_I+1
    setocc "UCFIELD",v_I
    IF($status<=0|$dbocc(UCFIELD)<=0) BREAK
    IF(P_FORMAT.UCFIELD  ="") P_FORMAT.UCFIELD  =$FMT_TRIGGER$
    IF(P_DEFORMAT.UCFIELD="") P_DEFORMAT.UCFIELD=$DFMT_TRIGGER$
  ENDWHILE
  store/e "UCFIELD"
END