Please be aware though, that there is NO security for stored procedures,
i.e. everyone has access to them. Recently I felt I absolutely needed a
stored procedure for my purposes and the only way to secure it was to create
a new namespace, place a registered class with the stored procedure in it,
create a sql user with access to the namespace only and switch on odbc
namespace security.

Wolf Koelling
Slaughter and May


"Luiz Papa" <papa at matrix dot inf dot br> wrote in message
news:[EMAIL PROTECTED]
> Tony,
>
> In my opinion you have two approachs:
> . Make a stored procedure (or query) for each routine you want to call (as
> Peter pointed);
> . Make a stored procedure that receives the name of a routine and calls
it.
>
> I think the first one is better for many reasons, but if you have many
> routines with very simple INPUT / OUTPUT the second would be very less
work.
>
> HTH,
> Luiz Papa
>
> "Tony Yates" <[EMAIL PROTECTED]> escreveu na mensagem
> news:[EMAIL PROTECTED]
> > Is it possible to call a routine using ODBC ? or do I have to use the
> > datafactory ?
> >
> > I have routines like ^acNDS which go away and do reports and move data
> > around.
> >
> > Many Thanks
> >
> > Regards
> >
> > Tony
> >
> >
>
>



Reply via email to