|
-- [ Picked text/plain from multipart/alternative ] Hello Booth, There are probably a number of ways to handle this, but one thing you might want to try is to lock down the physical file tightly so that the users can't access it. Then, create a logical (or logicals) over the physcial file that excludes rows where FERPA is filled in. You allow this logical to be accessed by the query runners and those accessing the data from outside the 400, and keep the original data in the physical file nice and secure. Hope this helps. Kevin Vandever.
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.
midrange.com
