Re: Updates...

->From: bobb@netcom.com (Bob Beaulieu) ->Subject: Updates... ->Date: Tue, 12 Jul 1994 17:38:08 GMT ->Organization: NETCOM On-line Communication Services (408 261-4700 guest) -> ... omitted ... -> ->I keep thinking that a user, (that knew how) could create a form using ->sformbld and update the data to whatever, bypassing the screen controls. -> ... omitted ... -> ->I thought about renaming sformbld to something else and write a c program ->named sformbld and if the req table is passed as a parameter, send an ->error: "Not authorized to create screens for req table!"; otherwise; ->pass the data to a system() call of the renamed sformbld. -> ->Any comments or ideas? -> ->Thanks, -> ->Bob ->bobb@netcom.com Do your users really need to be able to create their own forms? If so, your approach of renaming sformbld is complex but workable. If only your development group needs to create forms, then you might 'chgrp' the sformbld program to be group-owned by your development group and then 'chmod o-x,o-r sformbld' to remove execute and read access to sformbld from your users. Regards, Alan ___________________________ ______________________| R. Alan Popiel |__________________________ \\ Internet: | Martin Marietta, SLS | / \\ alan@den.mmc.com | P.O. Box 179, M/S 3810 | Std disclaimers apply. / )Voice: | Denver, CO 80201-0179 USA | ( / 303-977-9998 |___________________________| (But you knew that!) \\ /________________________) (____________________________\\