Weird fiePro Behavior

[Kenneth Brody]

George Simon wrote:
> 
> But, when allowing you to enter a field in the cursor path screen, it
> obviously does not stop when it finds that the first reference to the field
> is protected.  It obviously reads the rest of the screen.
> So why doesn't it do the same when a screen ,field_number statement is
> encountered?
> 
> And, why is it a "bad thing" to have the same field on the screen twice,
> once protected and once un-protected?

Because you have two copies of the field on the screen, each with a
different value.  Which one "wins"?

> And, if it is a "bad thing" just like writing to un-protected lookups, why
> do you allow it?

I'll be happy to disallow it if you want.  I'll just tell fpsupport to
forward all of the "why can't I do this anymore" questions to you.  ;-)

[...]

-- 
+-------------------------+--------------------+-----------------------------+
| Kenneth J. Brody        | www.hvcomputer.com |                             |
| kenbrody at spamcop.net | www.fptech.com     | #include <std_disclaimer.h> |
+-------------------------+--------------------+-----------------------------+