Re: ODBC Connections -- 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: ODBC Connections
From: Jerry Draper <midrangel@xxxxxxxxxxxxx>
Date: Tue, 02 Dec 2008 09:57:44 -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>

Wintermute, Sharon wrote:

I need to secure the ODBC connections to be read only. I am looking at
the Exit points and trying to figure this out. Can someone guide me?

Sharon Wintermute

There are several open source exit pgms availble. In general they are based on a file of allowed users that you maintain with a R)ead only or (Update allowed flag.

These pgms parse sql strings looking for sql update/add commands and act accordingly.

Jerry

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: ODBC Connections , Chris Bipes

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.