Weird fiePro Behavior

[Kenneth Brody]

George Simon wrote:
> 
> You can have the same field on a screen 2 or more times.

Yes, you can.  However, doing so is a "bad thing"[tm], unless all
instances are protected.  (Think of it like having multiple lookups
to the same record.)

> You can have one or several of the field instances protected.
> You can include the field in the cursor path, as long as one of the
> instances is unprotected.
> But you can’t have a statement in your processing such as:
> screen ,field_number
> unless the unprotected instance is higher than the protected one on the
> screen.
> 
> Why does filePro allow a field to be included in the cursor path and then
> ignore the contents of the cursor path when the screen statement is
> encountered?

It doesn't "ignore the contents of the cursor path".  The first instance
of the field on the screen is protected, and you can't enter a protected
field.

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