Re: 4GL replacement for isql menus

<massive snip to save bandwith> Q: Need to stop users getting to command line from ISQL user menus and perform screens using '!'. A1: set $SHELL to /dev/null in .profile/.login. but 1: then users can't run shell scripts from the user menu. 2: users could modify .profile/.login to overcome this. A2: make users access database using shell script that sets $SHELL to /dev/null. This solves 'but' 2, but not 'but' 1. (Hope this makes sense!). OK, now I've got my mind round the issues :-). This is a question that recurs fairly frequently on the list, and something that I've never found a solution to. However, something just popped into my head (and I'm thinking off the top of it now!!). What if the shell script that fires the database contains the line: unsetenv path (I'm using csh - I'm sure people can work out the Bourne shell equivalent). This will basically disable every command that is not in the current working directory. Then make sure that every command called in the application is called with its full path from the root directory (a practice I use already - every one of my users seems to have a different "standard" environment!!!). What do you all think? If this is totally ridiculous, just put it down to low blood sugar (it's just before Friday lunchtime, and my stomach is complaining!). Cheers, Richard.