Hmmm...
That must be the owners responsibility... Besides it's not that hard to define roles and permissions for a SQL Server-user (or any database).

So am I right when concluding that you've "hard-coded" away the possbility to use anything but SELECT? I know there ain't no such limitation using the ODBC-drivers.

We planned to mainly use our ListServ to send out mail to persons in our database using stored procedures, of course something your sales person thought would be no problem, in a manor like "send to all persons linked to this organisation, with this function and in this area" etc - often more complex than that...

It would have been very smooth if that had worked. :)
Now if you plan to do nothing about it and there ain't no way to unlock this limitation I have to solve it using a application to fill temp-tables with our SP-results and let ListServ talk to them instead.

Let me know.

Regards,
Johan

-----Ursprungligt meddelande-----
Från: Francoise Becker [mailto:[log in to unmask]] 
Skickat: den 16 maj 2003 17:59
Till: [log in to unmask]
Ämne: Re: stored procedure in mail-merge


On 16 May 2003, at 9:34, Johan Kronberg (n3sport) wrote:

> Hi!
>
> I'd still like to know why it's not possible to execute a SQL Server 
> stored procedure from listserv... Regular select statements work ok, 
> but not SP's...

Because it would be a HUGE security hole. Stored procedures are not limited to extracting data, they can also be made to change data.

Francoise