Re: Disable saving of Query/400 queries. -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: Disable saving of Query/400 queries.
From: Bill <brobins3d@xxxxxxxxx>
Date: Wed, 11 Feb 2009 10:10:39 -0800
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

rob@xxxxxxxxx wrote:

I know that you can restrict the running of Query/400 queries interactively by doing a CHGCMD on RUNQRY, however is there a way to allow someone to create a query, run it, but never save it?

Another idea might be to get a package like DBU's SQL4Less. If the user can deal with creating a query in SQL syntax, they can run adhoc and in batch mode all day long and never have to save them.

Bill

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Disable saving of Query/400 queries. , rob

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.