As I read the help, NODEFAULT (as long as its in the execution path) can go anywhere. It only is actually 'operated on' when all user code is completed.

Possibly donothing1() *does* do something - this person's way to maintain job security?!?!?

Cheers

JimN

>AFAIK, this does absolutely nothing. If it were a DODFAULT(), I could see the reasoning. If the NODEFAULT were the last thing, I could also see the reasoning (something like in a KEYPRESS event).
>
>>I found some code a previous programmer wrote that looks like:
>>
>>

>>this.dothing1()
>>NODEFAULT
>>this.dothing2()
>>

>>
>>What could the author possibly have in mind?
>>I see no reason for the NODEFAULT.
>>
>>It was at one point a FP 2.6 App.
>>
>>Just to increase understanding!
>>
>>Thanks