RE: Adopted authority and triggers -- MIDRANGE-L

Subject: RE: Adopted authority and triggers
From: "Elvis Budimlic" <ebudimlic@xxxxxxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 3 Apr 2007 23:40:42 -0500
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>

Way I understood, problem was that user didn't have authority to the library
where trigger program resides.

Celebrating 10-Years of SQL Performance Excellence

-----Original Message-----
Subject: RE: Adopted authority and triggers

As far as USEADPAUT goes, they could/should ignore system-state programs
and only adopt from user state programs, that would solve that problem,
no? Regardless, unless I misunderstood, the original poster wasn't able
to get the USRPRF(*OWNER) option to work either, correct?

-Walden

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Adopted authority and triggers , Mackie, Roger L. (Precision Press)

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.