What's the best way...
STEWARTM@dteenergy.com
STEWARTM@dteenergy.com
18 Mar 99 09:57:06 -0500
--=_ORCL_3485157_0_0
Content-Transfer-Encoding:quoted-printable
Content-Type:text/plain; charset="iso-8859-1"
Why are you changing the UPDATE procedure??? Don't do that. This is what
the
PREUPDATE procedure is for. What is wrong with a couple of lines of
procedural code? It better that maintaining two screens and that
conditional
compile crap.
Just do the following...(You can specify an ASC for a user instead of a
signonuser.)
IF NOT MATCHUSER("CERTAIN_ASC")
THEN
BEGIN
ERROR "*E* Only CETAIN_ASC can update."
END
If you want to do it for a particular field then put it in the EDIT
procedure
for that field.
Hope this helps.
----------------------
Mark Stewart
Consultants Club Corp.
Windsor, Ontario
Canada
--=_ORCL_3485157_0_0
Content-Type:message/rfc822
Date: 17 Mar 99 23:11:19
From:John Pearce <jpearce@rmi.net>
To:powerh-l
Subject:What's the best way...
Return-Path:<powerh-l-owner@lists.swau.edu>
Received:by mail.detroitedison.com with ESMTP id XAA04845; Wed, 17 Mar 1999 23:12:00 -0500 (EST)
Received:by dte.detroitedison.com with ESMTP id XAA28505; Wed, 17 Mar 1999 23:11:59 -0500 (EST)
Received:from sphere.swau.edu (sphere.swau.edu [205.165.192.254]) by cosmic3.swau.edu (8.8.3/8.8.3) with ESMTP id WAA06355; Wed, 17 Mar 1999 22:11:21 -0600
Received:from localhost (daemon@localhost) by sphere.swau.edu (8.9.1/8.9.1) with SMTP id WAA08115; Wed, 17 Mar 1999 22:11:06 -0600
Received:by sphere.swau.edu (bulk_mailer v1.9); Wed, 17 Mar 1999 22:10:11 -0600
Received:(from daemon@localhost) by sphere.swau.edu (8.9.1/8.9.1) id WAA08079 for powerh-l-outgoing; Wed, 17 Mar 1999 22:10:09 -0600
Received:from mg1.rockymtn.net (mailserv.rockymtn.net [166.93.205.11]) by sphere.swau.edu (8.9.1/8.9.1) with ESMTP id WAA07983 for <powerh-l@lists.swau.edu>; Wed, 17 Mar 1999 22:10:01 -0600
Received:from rainbow.rmi.net (rainbow [166.93.8.14]) by mg1.rockymtn.net (8.8.7/8.8.7) with ESMTP id VAA17346 for <powerh-l@lists.swau.edu>; Wed, 17 Mar 1999 21:09:57 -0700 (MST)
Received:from jlp (166-93-76-91.rmi.net [166.93.76.91]) by rainbow.rmi.net (8.8.7/8.8.5) with SMTP id VAA27588 for <powerh-l@lists.swau.edu>; Wed, 17 Mar 1999 21:09:53 -0700 (MST)
Message-Id:<4.1.19990317210315.00b2b220@rmi.net>
X-Sender:jpearce@rmi.net
Sender:owner-powerh-l@sphere.swau.edu
MIME-Version: 1.0
Content-Type:text/plain; charset=us-ascii
Content-Transfer-Encoding:7bit
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.
--=_ORCL_3485157_0_0--
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
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.