Create Logical Views over the files in question.  Make them a Join LF and
they become Read Only.  Give the users access to these files only.

Christopher K. Bipes    mailto:ChrisB@Cross-Check.com
Sr. Programmer/Analyst  mailto:Chris_Bipes@Yahoo.com
CrossCheck, Inc.        http://www.cross-check.com
6119 State Farm Drive   Phone: 707 586-0551 x 1102
Rohnert Park CA  94928  Fax: 707 586-1884

If consistency is the hobgoblin of little minds, only geniuses work here.
Karen Herbelin - Readers Digest 3/2000

-----Original Message-----
From: Shrader, Patrick [mailto:pshrader@wkep.com]
Sent: Thursday, November 09, 2000 11:02 AM
To: MIDRANGE-L@midrange.com
Subject: RE: ODBC Security


One ongoing question I have about this, and I am interested in suggestions,
is how can you limit access to specific fields using ODBC. I hope it does
not involve increasing my security level from 30.

I have an item master file that contains an item description and a cost.
While I want some users to be able to access the basic item information, I
don't want them to view costs. (This is a typical situation that can be
applied to many files). Is there a way to limit visibility on specific
fields in the file with ODBC?

As Rob said, green screens were much easier to secure -- but ODBC and Excel
really makes some reports easy for the users.

Patrick Shrader
+---
| 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
+---

This thread ...


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

This mailing list archive is Copyright 1997-2019 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].