Weird fiePro Behavior

[George Simon]

There are many work-arounds, I was just wondering why this is so or actually
"How does filePro determine if a field is protected?"
I guess it does it by reading the screen until it finds the first reference
to the field and then it makes its determination.  But why doesn't it apply
the same logic when accepting entries in the cursor path screen?

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: GCC Consulting [mailto:gcc at optonline.net]
Sent: Tuesday, April 20, 2004 11:09 AM
To: 'George Simon'; 'Filepro-List'
Subject: RE: Weird fiePro Behavior

George wrote:

You can have the same field on a screen 2 or more times.
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?

---------------------------------------------------------------------------
I can't answer your question.

However, you might consider using a protected dummy fields to display the
value
of the real unprotected field.  Then it won't matter where you place the
real
field on the screen.

Richard Kreiss
GCC Consulting