Double duty screens

[John Pearce]

I'm doing maintenance on a system written about 1990.  To provide certain
users the ability to view data but not to change it,  a dozen or so screens
were duplicated then all the procedure code deleted and the activities
statement changed to only allow find mode.  I need some ideas on making one
version of these screens perform double duty.  For certain user classes,
the screen should allow retrieval without update and allow other user
classes to enter and update, too.  

It seems like the only solution is to write a preupdate procedure that
checks the user's class and issues an error if update is not allowed.
While this approach will work, I'd prefer to issue an error message when
the user tries to update a field.   I don't want to write an input
procedure for each field on the screen either.  Is there an easy solution
for this?  Any other ideas beside the preupdate or input procedures?  FWIW,
this is PH8.19C4 on MPE/ix 5.5 PP 6.

Thanks. 

------------------------------------------------------------------
John Pearce  <jpearce@rmi.net>       | Bethesda Management Company 
Speaking for only myself             | Colorado Springs, CO  USA
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
This list is closed, thus to post to the list, you must be a subscriber.