Weird fiePro Behavior

George Simon george at worldest.com
Tue Apr 20 11:16:28 PDT 2004


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?
And, if it is a "bad thing" just like writing to un-protected lookups, why
do you allow it?

George Simon (IT Department)
American River Logistics, LTD
614 Progress St.
Elizabeth, NJ  07205
Phone:(908)354-7746      Fax:(908)354-7491
mailto:george at worldest.com
http://www.americanriverintl.com/



-----Original Message-----
From: Kenneth Brody [mailto:kenbrody at bestweb.net]
Sent: Tuesday, April 20, 2004 11:31 AM
To: George Simon
Cc: Filepro-List
Subject: Re: Weird fiePro Behavior

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>
|
+-------------------------+--------------------+----------------------------
-+



More information about the Filepro-list mailing list