By: TomLiotta

TomLiotta — Tue, 17 Jul 2012 21:20:35 +0000

QM queries seem to be the way to go, though there’s no need to create QM queries for them. Just let them use the STRQM command and restrict them from using STRSQL. I don’t recall a way to restrict statements in STRSQL. (There shouln’t be a need to restrict statements. Users shouldn’t have the authority to cause damage with SQL statements, so there shouldn’t be a reason to limit statements.)

With QM, an administrator can choose the SQL statements that any user can run. Just set SELECT as the only allowed statement. You might also set the user’s default mode to SQL, and also allow the user to switch to prompted mode if desired.

The user can then enter a SELECT statement, get practically the same statement prompting assistance as with STRSQL, and save queries if desired.

The big loss is the statement history. But if the history only contains a few different SELECT statements, users might choose just to save each one in their own QM query objects.

Tom

By: BigKat

BigKat — Tue, 17 Jul 2012 11:34:22 +0000

are they “fixed” commands (i.e. the same everytime) – create them in QMQRY queries, and add them to a menu for them.
if they have to enter varying parameters (e.g. different customer numbers) you can do that as well. You will just need to create a “wrapper” program to prompt for the parameters, and then call the query passing it those values.

Comments on: Is it possible to give a user access to sql screen wherein he is allowed only to use select commands

By: TomLiotta

By: BigKat