What we did in a similar situation, is to grant Listserv only Read permission
over the table/s. Since it is the Data Warehouse anyhow that updates the
records of the table, listserv need not do it. Mind you, an error
message will still be generated, but that would alert the user to the fact
they can't change their settings, neither subscribe of sign-off of course...
Moshe

> Date: Fri, 9 Apr 2004 16:47:56 -0400
> From: "Rakauskas, George R." <[log in to unmask]>
> Reply-To: LISTSERV give-and-take forum <[log in to unmask]>
> To: [log in to unmask]
> Subject: Block users from Subscription Settings when using DBMS table
>
> We have several employee-related lists that I would like to generate out
> of one main table that is defined in our HR Oracle Data Warehouse.
> I have defined a view on this table for each list with the appropriate
> selection criteria.
> Each list header then has DBMS = Yes, Table(VW_LS_xxxxxxx),...
>
> In some cases, it would be appropriate to use DISTINCT in the selection
> criteria.
> This renders the view un-updatable.So if a user tries to change their
> options in Subscription Settings they get a nasty DBMS ERROR that we
> would prefer to avoid.
>
> In fact, we would rather that the users not be able to change
> Subscription Settings at all for these automated lists.
>
> Is there a way to block users from being able to change subscription
> Settings for certain lists?
>
>
> George R. Rakauskas
>
>