|
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
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.