What's the best way...

[John Pearce]

What's the best way to have a single screen serve two sets of users (based
on user class) where one user class can do everything (enter, update,
delete) and the other user class can only inquire on existing records?

If, for example, I put procedure code into the UPDATE procedure to check
the user class, the inquiry users will be able to make changes on the
screen yet the update will fail.  Since this approach requires procedure
code in several procedures, the code and its maintenance may be more
trouble that having two sets of screens.

What am I missing???  Is there a better way to accomplish this???  Running
8.19C3 on HP.



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