Re: Blocking QM Queries Was: WRKQRY - getting the SELECT records date range to show in the title

Rob

The STRQM authorizations only block what can be done in that interface, Query Manager. Anyone can create a source file with RCDLEN(91), put any SQL statement in a member, and run CRTQMQRY against that to compile a QMQRY. Same with forms, but with RCDLEN(162) and the fact that no one in his right mind knows how to enter the specs for forms by hand.

So this restriction is restricted in its ability to restrict things, right? Nonetheless, it's a start, and maybe people won't learn about the CRTQMQRY command!! For me, this has been just a phantom with no power.

Vern

On 7/21/2010 2:34 PM, rob@xxxxxxxxx wrote:

I see no need to block QM Queries any more than I see blocking Query/400,
Excel or any other host of reporting tools.

I can see blocking PARTS of QM Query. QM Query is not limited to SELECT.
It can also do UPDATE, INSERT, etc. But this is easily handled by
STRQM
10. Work with Query Manager profiles
2=Change
Select allowed SQL statements
The default is to only give them SELECT (unless they are an older user
migrated from V2R1).

Wouldn't you like this simple process in Query/400?
2=Basic
Grants ... limited access to the queries and report forms options.
Users can display and print query and report form definitions, and run
queries and reports, but they cannot create or change them.

Or change their "Display run options" to block them from outputting over
top an existing file?


Rob Berendt