In message <[log in to unmask]>, John Pollard
<[log in to unmask]> writes
>I am using Reflection for HP v6.0, for both the "before" and "after" tests;
>with no settings changes in between. (And MPE/iX 6.0)
>
>I believe the problem is within the forms file and/or FORMSPEC.
>
>The form in question is a member of a forms family. I have discovered that
>even if all I do is display the parent form on the screen in FORMSPEC and
>press the enter key, then compile - the resulting forms file has
>been "changed", even though I have not keyed any changes to the forms file.
>
>And, it appears to me (from doing an FCOPY hex/char of the resultant forms
>file) that the enhancements for the password field are different after
>doing the compile. The "description of the enhancements" (FORMSPEC codes
>like "S" for security, "U" for underline) for the password field in the
>resulting forms file (as seen by FCOPY) seem to be the same, but the escape
>sequences for the password field have been changed.
>
>I can not understand why pressing the enter key on a screen definition (in
>FORMSPEC) and doing a compile of the forms file should change *anything* if
>I have not made any changes to the forms file - much less reconstruct the
>escape sequences for a field.
Well, I can answer half of this - if you press 'Enter' on a form, or any
field on a form, VPLUS takes that as a 'touch', and marks it for
recompilation.
If you don't want this to happen, read the forms using only the other
function keys - Next and Previous, field or Form, don't have this
effect.
And a half-answer of the other point is that this could happen if you
were doing the new compile in a later copy of VPLUS, which might well
have addressed some issues regarding escape sequence sequencing.
Were you?
--
Roy Brown 'Have nothing in your houses that you do not know to be
Kelmscott Ltd useful, or believe to be beautiful' William Morris
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
