next »

[.]

Hi Seb,

As I said, I don't use TABINDEX=0 often (though probably should thinking about it) so wasn't overly sure on it's behaviour.

Based upon what you've said I agree the field should be ignored for NEXT FIELD START/END. Basically, as an application developer if you hard code to ignore it at the start then you want it to be consistently ignored. (If however, you make a field inactive from the start and then make it active you would NOT want that ignored).

As I said before, not that bothered what you call it if it works. START/END and FIRST/LAST are fine by me and as long as they're clearly documented people should cope.

Another way to go (purely suggestion if NEXT FIELD START isn't liked) is to keep the DIALOG one completely seperate with:
    CALL DIALOG.nextFieldFirst()
    CONTINUE DIALOG

which I think would sit with much of the way multiple dialog's are handled and reserve NEXT FIELD FIRST/LAST purely for the sub-dialogs.

Jeff