Weird fiePro Behavior

[George Simon]

>George,

>It seems that in your application, you accidentally placed the same
>field on the screen twice.  The cursor path allowed you to list it
>because it was on the screen, but because it is not usually a reasonable
>practice to do this, you are complaining because the
>SCREEN ,field logic did not work.

>I think that most of us would consider that a programmer mistake and
>would not expect filePro to catch it as a mistake or error.

Nancy, the field was put on the screen twice on purpose.  Once protected and
once unprotected.
I'm not saying it is a filePro bug and the logic did work, it just did not
take me to the field intended.

All I was asking is why filePro employs, what seems to me, different logic
when it allows you to place a field in the cursor path screen that is
protected in at least one instance but will not go to that same field when
you do a screen ,field_number from processing IF the protected copy appears
before the unprotected one on the screen.

I was just wondering how filePro determines if a field is protected or not.
Like I said, it seems to employ two different methods.