HP3000-L Archives

February 2002, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
John Pollard <[log in to unmask]>
Reply To:
John Pollard <[log in to unmask]>
Date:
Wed, 20 Feb 2002 18:22:53 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (25 lines)
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.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2