|
I don't think it would work in your situation, but what we've managed to do so far is restrict end users' access to the name and address master to applications available from a menu. Otherwise it requires a request for an ad hoc job. We're screening both explicit requests for do not mail or rent as well as inclusion in the DMA opt out file. I think most companies that work with direct mail take this sort of thing seriously. Aside from the ill will and possible legal action, there's the cost of mailing a catalog or brochure to someone you know is not going to look at it. > -----Original Message----- > From: York, Albert [mailto:albert.york@nissan-usa.com] > Sent: Wednesday, January 23, 2002 9:31 AM > To: 'midrange-l@midrange.com' > Subject: RE: Use of a trigger...? is this areasonable? > > > The easiest way that I can think of is to create a logical > file excluding > FERPA records and only give access to the logical file. > > Albert York > > > -----Original Message----- > From: Booth Martin [SMTP:booth@MartinVT.com] > Sent: Wednesday, January 23, 2002 9:21 AM > To: midrange-l@midrange.com > Subject: Use of a trigger...? is this areasonable? > > > > I've just been handed a problem and first blush tells me that a > trigger is > the answer, but I sure would like to hear comments from > people on > the list > that have already dealt with this sort of problem. > > Here's the deal: our name and address file has a field > in their for > FERPA. > If its marked then the name can not be listed or generally > distributed > without that person's written permission. This has > worked fine for > years > when we only accessed the information with our RPG programs. > > Now though we have users with Query and other methods > of accessing > the file, > and these users just ignore the FERPA field. The results are > labelled > Trouble waitng to happen". > > What ways would you folks offer as ways to prevent > access to that > record if > FERPA is chosen? (I'm thinking this is a question all of us are > facing > lately) > > > > -------------------------------------------- > Booth Martin > MartinB@Goddard.edu > 802-454-8315 x235 > -------------------------------------------- > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) > mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > _______________________________________________ > This is the Midrange Systems Technical Discussion > (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. >
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.