× 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: Limiting SQL Access
  • From: "Fisher, Don" <DRF@xxxxxxxxxxxxxxxx>
  • Date: Tue, 28 Nov 2000 07:44:00 -0500

Unfortunately, securing the command really doesn't help.  It is easy to use
a CL program to invoke a QMQRY object to execute SQL statements.  If I may
say so, it sounds like your real problem is securing your production files
from update via unauthorized means.

Donald R. Fisher, III
Project Manager
Heilig-Meyers Furniture Company
(804) 784-7500 ext. 2124
Don.Fisher@HeiligMeyers.com

At 12:56 AM 11/28/2000, you wrote:
>I would like to restrict the usage of SQL. Since we had some abuse on SQL
<clip>

Why not just secure the command?

david
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.